Hi, I've run the attached test case on a clean 4.0 and 4.0 + the patch you referenced but in neither cases could I crash the kernel. All that was happening was for a new namespace to be created and bash executed in it and after some seconds I get logged out of the machine. But then I can log-in back and the kernel hasn't crashed. Regards, Nikolay On 05/27/2015 06:16 PM, Eric W. Biederman wrote: > Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> writes: > >> On Tue, May 26, 2015 at 12:31 PM, Eric W. Biederman >> <ebiederm@xxxxxxxxxxxx> wrote: >>> Alexander Larsson <alexl@xxxxxxxxxx> writes: >>> >>>> On mån, 2015-05-18 at 16:39 +0200, Alexander Larsson wrote: >>>> >>>> Didn't get any replies to the below kernel panic (testcase attached), >>>> which seems rather important to fix. Reposting to a wider audience. >>> >>> Buggered backport greg already has the fix somewhere in his queue. >> >> Is it fs_pin-allow-for-the-possibility-that-m_list-or-s_list-go-unused.patch >> or mnt-fail-collect_mounts-when-applied-to-unmounted-mounts.patch ? >> (Or both I guess.) Those are the only 2 patches queued for 4.0 stable >> right now. > > Both fix the buggered backport. > > fs_pin-allow-for-the-possibility-that-m_list-or-s_list-go-unused.patch > fixes the crash. > > Eric > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
