linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: viro@ZenIV.linux.org.uk, npiggin@kernel.dk,
	linux-fsdevel@vger.kernel.org
Subject: Re: [2.6.38] Deadlock between rename_lock and vfsmount_lock.
Date: Wed, 23 Mar 2011 17:10:37 -0700	[thread overview]
Message-ID: <20110324001037.GA2122@kroah.com> (raw)
In-Reply-To: <201103240004.p2O04SWm065278@www262.sakura.ne.jp>

On Thu, Mar 24, 2011 at 09:04:28AM +0900, Tetsuo Handa wrote:
> Greg KH wrote:
> > On Sat, Mar 19, 2011 at 11:39:19AM +0900, Tetsuo Handa wrote:
> > > Al Viro wrote:
> > > > 	See #untested in vfs-2.6.git.  I think it should do it, but
> > > > it *is* completely untested at the moment.
> > > 
> > > As far as I can test, I did not find any problems. Thank you.
> > 
> > Did this fix go to Linus?  If so, any pointers to the git commit id?
> 
> It is commit 27cb1572e3e6bb1f8cf6bb3d74c914a87b131792 "fix deadlock in pivot_root()"
> in linux-2.6.git .
> 
> > I'm guessing I will want this in the .38-stable tree?
> 
> Yes. We are waiting for tests by Al.

Great, thanks for letting me know, I'll watch out for the above patch to
hit Linus's tree.

greg k-h

      reply	other threads:[~2011-03-24  0:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16  8:54 [2.6.38] Possible deadlock at pivot_root? Tetsuo Handa
2011-03-17  5:01 ` [2.6.38] Deadlock between rename_lock and vfsmount_lock Tetsuo Handa
2011-03-18 10:59   ` Tetsuo Handa
2011-03-18 11:06     ` Al Viro
2011-03-18 11:54       ` Tetsuo Handa
2011-03-18 12:07       ` Al Viro
2011-03-18 12:13         ` Al Viro
2011-03-18 12:52         ` Al Viro
2011-03-18 13:18           ` Al Viro
2011-03-19  2:39             ` Tetsuo Handa
2011-03-23 23:00               ` Greg KH
2011-03-24  0:04                 ` Tetsuo Handa
2011-03-24  0:10                   ` 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=20110324001037.GA2122@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=npiggin@kernel.dk \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=viro@ZenIV.linux.org.uk \
    /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).