From: ebiederm@xmission.com (Eric W. Biederman)
To: 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: Wed, 27 May 2015 10:16:14 -0500 [thread overview]
Message-ID: <87pp5mqce9.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <CA+5PVA7wpFwMSHkAQoVzthYSrxJXfpZo5vLGKYAHggN+ujJyow@mail.gmail.com> (Josh Boyer's message of "Wed, 27 May 2015 10:06:53 -0400")
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
next prev parent reply other threads:[~2015-05-27 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1431959951.5030.2.camel@redhat.com>
2015-05-26 12:19 ` Kernel panic with user namespaces Alexander Larsson
2015-05-26 16:31 ` Eric W. Biederman
2015-05-27 14:06 ` Josh Boyer
2015-05-27 15:16 ` Eric W. Biederman [this message]
2015-05-28 7:03 ` Nikolay Borisov
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=87pp5mqce9.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=alexl@redhat.com \
--cc=containers@lists.linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox