stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alexandr Morozov <alexandr.morozov@docker.com>
Cc: stable@vger.kernel.org
Subject: Re: Fix for kernel crash
Date: Wed, 20 May 2015 15:54:47 -0700	[thread overview]
Message-ID: <20150520225447.GA17702@kroah.com> (raw)
In-Reply-To: <CA+EAOG7ghvcXvXNz3hie9vcXc1BYS3Fj2sCM2_oVBa58YcCEug@mail.gmail.com>

On Wed, May 20, 2015 at 02:36:16PM -0700, Alexandr Morozov wrote:
> Commit 820f9f147dcce2602eefd9b575bbbd9ea14f0953 (fs_pin: Allow for the
> possibility that m_list or s_list go unused) in main kernel tree fixes
> kernel crash.
> I encountered this crash when ran test on libcontainer project. Seems
> like some problem with mounts under nested user-namespaces. It was
> introduced in 4.0.2.

It's already queued up, thanks!

greg k-h

      reply	other threads:[~2015-05-20 22:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 21:36 Fix for kernel crash Alexandr Morozov
2015-05-20 22:54 ` Greg KH [this message]

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=20150520225447.GA17702@kroah.com \
    --to=greg@kroah.com \
    --cc=alexandr.morozov@docker.com \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).