public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs fix
Date: Sun, 31 May 2015 22:37:25 +0100	[thread overview]
Message-ID: <20150531213725.GI7232@ZenIV.linux.org.uk> (raw)

Off-by-one in d_walk()/__dentry_kill() race fix.  It's very hard to hit;
possible in the same conditions as the original bug, except that you
need the skipped branch to contain all the remaining evictables, so that
the d_walk()-calling loop in d_invalidate() decides there's nothing more
to do and doesn't go for another pass - otherwise that next pass will
sweep the sucker.  So it's not too urgent, but seeing that the fix is obvious
and the original commit has spread into all -stable branches...
Please, pull from

git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus

Shortlog:
Al Viro (1):
      d_walk() might skip too much

Diffstat:
 fs/dcache.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

             reply	other threads:[~2015-05-31 21:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31 21:37 Al Viro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-27  1:13 [git pull] vfs fix Al Viro
2016-11-27  1:48 ` Linus Torvalds
2016-11-27  2:25   ` Al Viro
2016-11-27  2:51     ` Al Viro
2016-11-27  3:04       ` Al Viro
2016-11-28  8:54       ` Yan, Zheng
2016-11-27  2:53     ` Linus Torvalds
2016-03-31  4:27 Al Viro
2011-11-22 17:44 Al Viro
2011-11-22 17:48 ` Linus Torvalds
2011-11-22 21:09   ` Al Viro
2011-11-22 21:24     ` Linus Torvalds
2011-08-07  8:54 Al Viro
2011-02-24  7:20 Al Viro

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=20150531213725.GI7232@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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