From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCHES] namei cleanups
Date: Tue, 8 Jun 2021 11:38:40 +0000 [thread overview]
Message-ID: <YL9WwAD547fY19EE@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.
next reply other threads:[~2021-06-08 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 11:38 Al Viro [this message]
2021-06-08 11:39 ` [PATCH 1/4] switch file_open_root() to struct path Al Viro
2021-06-08 11:39 ` [PATCH 2/4] take LOOKUP_{ROOT,ROOT_GRABBED,JUMPED} out of LOOKUP_... space Al Viro
2021-06-08 11:39 ` [PATCH 3/4] teach set_nameidata() to handle setting the root as well Al Viro
2021-06-08 11:39 ` [PATCH 4/4] namei: make sure nd->depth is always valid Al Viro
2021-06-08 12:12 ` [PATCHES] namei cleanups Christian Brauner
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=YL9WwAD547fY19EE@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).