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.git pile 3 - dcache
Date: Wed, 3 Aug 2022 19:39:25 +0100 [thread overview]
Message-ID: <YurA3aSb4GRr4wlW@ZenIV> (raw)
The following changes since commit b13baccc3850ca8b8cccbf8ed9912dbaa0fdf7f3:
Linux 5.19-rc2 (2022-06-12 16:11:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-work.dcache
for you to fetch changes up to 50417d22d0efbb1be76c3cb66b2329f83741c9c7:
fs/dcache: Move wakeup out of i_seq_dir write held region. (2022-07-30 00:38:16 -0400)
----------------------------------------------------------------
Main part here is making parallel lookups safe for RT - making
sure preemption is disabled in start_dir_add()/ end_dir_add() sections (on
non-RT it's automatic, on RT it needs to to be done explicitly) and moving
wakeups from __d_lookup_done() inside of such to the end of those sections.
Wakeups can be safely delayed for as long as ->d_lock on in-lookup
dentry is held; proving that has caught a bug in d_add_ci() that allows
memory corruption when sufficiently bogus ntfs (or case-insensitive xfs)
image is mounted. Easily fixed, fortunately.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (1):
d_add_ci(): make sure we don't miss d_lookup_done()
Sebastian Andrzej Siewior (3):
fs/dcache: Disable preemption on i_dir_seq write side on PREEMPT_RT
fs/dcache: Move the wakeup from __d_lookup_done() to the caller.
fs/dcache: Move wakeup out of i_seq_dir write held region.
fs/dcache.c | 54 ++++++++++++++++++++++++++++++++++++++++----------
include/linux/dcache.h | 9 +++------
2 files changed, 46 insertions(+), 17 deletions(-)
next reply other threads:[~2022-08-03 18:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 18:39 Al Viro [this message]
2022-08-03 18:57 ` [git pull] vfs.git pile 3 - dcache Linus Torvalds
2022-08-03 19:49 ` Al Viro
2022-08-03 21:54 ` Steven Rostedt
2022-08-03 22:09 ` Linus Torvalds
2022-08-03 22:59 ` Steven Rostedt
2022-08-03 23:24 ` Matthew Wilcox
2022-08-03 23:42 ` Linus Torvalds
2022-08-04 0:42 ` Matthew Wilcox
2022-08-04 1:32 ` Steven Rostedt
2022-08-04 2:16 ` Linus Torvalds
2022-08-04 10:52 ` Steven Rostedt
2022-08-08 22:06 ` Thomas Gleixner
2022-08-08 22:43 ` Linus Torvalds
2022-08-09 16:00 ` Thomas Gleixner
2022-08-09 16:15 ` Matthew Wilcox
2022-08-09 17:58 ` Thomas Gleixner
2022-08-03 19:00 ` pr-tracker-bot
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=YurA3aSb4GRr4wlW@ZenIV \
--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 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.