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 more namei.c stuff
Date: Sat, 3 Jul 2021 03:01:11 +0000 [thread overview]
Message-ID: <YN/S94w08pU0tZbq@zeniv-ca.linux.org.uk> (raw)
Small namei.c patch series, mostly to simplify the rules
for nameidata state. It's in #work.namei and it's actually from
the previous cycle - didn't post it for review in time...
Changes visible outside of fs/namei.c: file_open_root()
calling conventions change, some freed bits in LOOKUP_... space.
The following changes since commit 4f0ed93fb92d3528c73c80317509df3f800a222b:
LOOKUP_MOUNTPOINT: we are cleaning "jumped" flag too late (2021-04-06 20:33:00 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.namei
for you to fetch changes up to 7962c7d196e36aa597fadb78c1cb4fe7e209f803:
namei: make sure nd->depth is always valid (2021-04-07 13:57:17 -0400)
----------------------------------------------------------------
Al Viro (4):
switch file_open_root() to struct path
take LOOKUP_{ROOT,ROOT_GRABBED,JUMPED} out of LOOKUP_... space
teach set_nameidata() to handle setting the root as well
namei: make sure nd->depth is always valid
Documentation/filesystems/path-lookup.rst | 6 +--
Documentation/filesystems/porting.rst | 9 ++++
arch/um/drivers/mconsole_kern.c | 2 +-
fs/coredump.c | 4 +-
fs/fhandle.c | 2 +-
fs/internal.h | 2 +-
fs/kernel_read_file.c | 2 +-
fs/namei.c | 80 +++++++++++++++++--------------
fs/nfs/nfstrace.h | 4 --
fs/open.c | 4 +-
fs/proc/proc_sysctl.c | 2 +-
include/linux/fs.h | 8 +++-
include/linux/namei.h | 3 --
kernel/usermode_driver.c | 2 +-
14 files changed, 74 insertions(+), 56 deletions(-)
next reply other threads:[~2021-07-03 3:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 3:01 Al Viro [this message]
2021-07-03 19:40 ` 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=YN/S94w08pU0tZbq@zeniv-ca.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
all inboxes | Powered by JetHome®