From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [git pull] vfs.git pile 1 - namei stuff
Date: Mon, 1 Aug 2022 21:17:11 +0100 [thread overview]
Message-ID: <Yug0x5GvaInf3opV@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.namei
for you to fetch changes up to 3bd8bc897161730042051cd5f9c6ed1e94cb5453:
step_into(): move fetching ->d_inode past handle_mounts() (2022-07-06 13:16:07 -0400)
----------------------------------------------------------------
RCU pathwalk cleanups. Storing sampled ->d_seq of
the next dentry in nameidata simplifies life considerably,
especially if we delay fetching ->d_inode until step_into().
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (10):
__follow_mount_rcu(): verify that mount_lock remains unchanged
namei: get rid of pointless unlikely(read_seqcount_retry(...))
follow_dotdot{,_rcu}(): change calling conventions
switch try_to_unlazy_next() to __legitimize_mnt()
namei: move clearing LOOKUP_RCU towards rcu_read_unlock()
namei: stash the sampled ->d_seq into nameidata
step_into(): lose inode argument
follow_dotdot{,_rcu}(): don't bother with inode
lookup_fast(): don't bother with inode
step_into(): move fetching ->d_inode past handle_mounts()
fs/mount.h | 1 -
fs/namei.c | 191 +++++++++++++++++++++++++--------------------------------
fs/namespace.c | 2 +-
3 files changed, 86 insertions(+), 108 deletions(-)
next reply other threads:[~2022-08-01 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 20:17 Al Viro [this message]
2022-08-03 19:00 ` [git pull] vfs.git pile 1 - namei stuff 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=Yug0x5GvaInf3opV@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).