All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: npiggin@kernel.dk, linux-fsdevel@vger.kernel.org
Subject: Re: [2.6.38] Deadlock between rename_lock and vfsmount_lock.
Date: Fri, 18 Mar 2011 12:52:24 +0000	[thread overview]
Message-ID: <20110318125224.GJ22723@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20110318120748.GH22723@ZenIV.linux.org.uk>

On Fri, Mar 18, 2011 at 12:07:48PM +0000, Al Viro wrote:
> lock_mount(path, follow)
> retry:
> 	lock path->dentry->d_inode
> 	if unlikely(can't mount)
> 		unlock
> 		fail
> 	grab namespace_sem
> 	if !follow || likely(lookup_mnt() returns NULL)
> 		we are done
> 	drop namespace_sem
> 	unlock
> 	drop path
> 	replace it with result of lookup_mnt() (and its ->mnt_root)
> 	goto retry;
> 
> and use that (local to fs/namespace.c) in do_add_mount()/do_move_mount()/
> do_loopback() (with follow = 1) and pivot_root() (follow = 0).  BTW,
> the lack of following in do_loopback() looks like a bug...

So's the lack of following on old in pivot_root, actually.  IOW, follow
argument is always 1...

  parent reply	other threads:[~2011-03-18 12:52 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 [this message]
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

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=20110318125224.GJ22723@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=npiggin@kernel.dk \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    /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.