From: Nikolay Borisov <kernel@kyup.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
Josh Boyer <jwboyer@fedoraproject.org>
Cc: Alexander Larsson <alexl@redhat.com>,
containers@lists.linux-foundation.org,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: Kernel panic with user namespaces
Date: Thu, 28 May 2015 10:03:32 +0300 [thread overview]
Message-ID: <5566BDC4.4020909@kyup.com> (raw)
In-Reply-To: <87pp5mqce9.fsf@x220.int.ebiederm.org>
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@fedoraproject.org> writes:
>
>> On Tue, May 26, 2015 at 12:31 PM, Eric W. Biederman
>> <ebiederm@xmission.com> wrote:
>>> Alexander Larsson <alexl@redhat.com> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2015-05-28 7:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 14:39 Kernel panic with user namespaces Alexander Larsson
[not found] ` <1431959951.5030.2.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-26 12:19 ` Alexander Larsson
2015-05-26 12:19 ` Alexander Larsson
[not found] ` <1432642765.19400.2.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-26 16:31 ` Eric W. Biederman
2015-05-26 16:31 ` Eric W. Biederman
2015-05-27 14:06 ` Josh Boyer
[not found] ` <CA+5PVA7wpFwMSHkAQoVzthYSrxJXfpZo5vLGKYAHggN+ujJyow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-27 15:16 ` Eric W. Biederman
2015-05-27 15:16 ` Eric W. Biederman
2015-05-28 7:03 ` Nikolay Borisov [this message]
[not found] ` <87pp5mqce9.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2015-05-28 7:03 ` Nikolay Borisov
[not found] ` <87vbff1es3.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2015-05-27 14:06 ` Josh Boyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5566BDC4.4020909@kyup.com \
--to=kernel@kyup.com \
--cc=alexl@redhat.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.