All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git fixes
Date: Sun, 12 Aug 2018 18:44:47 +0100	[thread overview]
Message-ID: <20180812174445.GL6515@ZenIV.linux.org.uk> (raw)

	A bunch of race fixes, mostly around lazy pathwalk.  All of that
is -stable fodder, large part going back to 2013 ;-/

The following changes since commit 9ba546c01976a426292af99e682a557075d6c010:

  aio: don't expose __aio_sigset in uapi (2018-07-17 23:26:58 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes

for you to fetch changes up to 4c0d7cd5c8416b1ef41534d19163cb07ffaa03ab:

  make sure that __dentry_kill() always invalidates d_seq, unhashed or not (2018-08-09 18:07:15 -0400)

----------------------------------------------------------------
Al Viro (4):
      root dentries need RCU-delayed freeing
      fix mntput/mntput race
      fix __legitimize_mnt()/mntput() race
      make sure that __dentry_kill() always invalidates d_seq, unhashed or not

 fs/dcache.c    | 13 ++++++-------
 fs/namespace.c | 28 ++++++++++++++++++++++++++--
 2 files changed, 32 insertions(+), 9 deletions(-)

             reply	other threads:[~2018-08-12 20:23 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-12 17:44 Al Viro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-25  6:59 [git pull] vfs.git fixes Al Viro
2024-02-25 17:58 ` pr-tracker-bot
2023-03-10 20:27 Al Viro
2023-03-11  4:52 ` pr-tracker-bot
2021-01-17  3:21 Al Viro
2021-01-17 20:20 ` pr-tracker-bot
2020-10-11 18:06 Al Viro
2020-10-11 18:23 ` pr-tracker-bot
2020-04-28 21:18 Al Viro
2020-04-28 21:45 ` pr-tracker-bot
2020-03-12 22:37 Al Viro
2020-03-12 23:00 ` pr-tracker-bot
2020-02-24  0:22 Al Viro
2020-02-24 20:25 ` pr-tracker-bot
2020-01-26 18:25 Al Viro
2020-01-26 19:30 ` pr-tracker-bot
2019-11-24 20:05 Al Viro
2019-11-25  0:35 ` pr-tracker-bot
2019-11-15  0:50 Al Viro
2019-11-15 17:35 ` pr-tracker-bot
2019-05-05  2:18 Al Viro
2019-05-05 22:10 ` pr-tracker-bot
2019-03-03  3:42 Al Viro
2019-03-03 20:21 ` Linus Torvalds
2019-03-04 21:30 ` pr-tracker-bot
2018-11-30  5:15 Al Viro
2018-11-30 21:00 ` pr-tracker-bot
2018-05-21 18:39 Al Viro
2018-05-21 18:59 ` Linus Torvalds
2018-03-16  1:41 Al Viro
2017-10-22  0:12 Al Viro
2017-10-11  4:54 Al Viro
2017-10-11 17:47 ` Vitaly Mayatskikh
2017-05-21 17:24 Al Viro
2017-04-27  7:34 Al Viro
2016-07-12  5:16 Al Viro
2016-07-01 20:51 Al Viro
2015-12-06 17:40 Al Viro
2015-11-25 23:08 Al Viro
2015-01-25  2:39 Al Viro
2014-11-22  4:43 Al Viro
2014-11-06  5:04 Al Viro
2013-11-11 16:30 [git pull] vfs.git Al Viro
2013-11-13 13:17 ` [git pull] vfs.git fixes 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=20180812174445.GL6515@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@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 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.