All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Matthew Wilcox <willy@infradead.org>
Cc: Eric Biggers <ebiggers3@gmail.com>,
	linux-fsdevel@vger.kernel.org,
	John Ogness <john.ogness@linutronix.de>,
	Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH vfs/for-next] fs/dcache.c: fix NULL pointer dereference in shrink_lock_dentry()
Date: Sat, 24 Mar 2018 04:50:54 +0000	[thread overview]
Message-ID: <20180324045054.GL30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20180324043735.GB22733@bombadil.infradead.org>

On Fri, Mar 23, 2018 at 09:37:35PM -0700, Matthew Wilcox wrote:
> On Fri, Mar 23, 2018 at 04:04:43PM -0700, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> > 
> > We can reach 'out:' with a negative dentry, e.g. if there is contention
> > on ->d_parent->d_lock and another task concurrently gets a reference to
> > the negative dentry.  In that case 'inode' will be NULL, so we must not
> > try to unlock 'inode'.
> > 
> > This bug was found by xfstest generic/429.
> 
> hmm ... I'd rather see:
> 
> 	if (unlikely(parent != dentry->d_parent)) {
> 		spin_unlock(&parent->d_lock);
> 		spin_lock(&dentry->d_lock);
> -		goto out;
> +		if (inode)
> +			goto out;
> +		return false;
> 	}
> 	spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED);
> 	if (likely(!dentry->d_lockref.count))
> 		return true;
> 	spin_unlock(&parent->d_lock);
> out:
> 	spin_unlock(&inode->i_lock);
> 	return false;
> 
> That puts the comparison out-of-line rather than in the exit path that
> everybody uses.

That was my first reaction as well, but...  we can get there without parent
changing - just a negative dentry that got grabbed by somebody else just
as we'd been getting its ->d_lock.  Moreover, this is _not_ the exit path
everyone takes - all paths reaching it go though an unlikely branch.
The common ones are actually "got all locks, everything's stable, nobody
has grabbed any references" (return true a couple of lines prior) or
"the sucker has grown references while it sat on the shrink list" as the
second (considerably more rare) option (the very first return false in
that function).

To get to out: we need the damn thing touched by somebody else while we
were *inside* shrink_lock_dentry().  And it's a narrow window (note that
we do not have trylock loops there anymore).

So Eric's patch is the right solution; I've folded it in, with credits in
updated commit message.  Will push tonight or tomorrow...

  reply	other threads:[~2018-03-24  4:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 23:04 [PATCH vfs/for-next] fs/dcache.c: fix NULL pointer dereference in shrink_lock_dentry() Eric Biggers
2018-03-24  4:37 ` Matthew Wilcox
2018-03-24  4:50   ` Al Viro [this message]
2018-03-24 11:35     ` Matthew Wilcox

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=20180324045054.GL30522@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=willy@infradead.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.