From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-fsdevel@vger.kernel.org
Cc: linux-nfs@vger.kernel.org, Jeff Layton <jlayton@kernel.org>,
NeilBrown <neil@brown.name>
Subject: [PATCHES] nfsctl fix and cleanups
Date: Thu, 11 Sep 2025 23:44:29 +0100 [thread overview]
Message-ID: <20250911224429.GX39973@ZenIV> (raw)
More stuff pulled out of tree-in-dcache pile, this time nfsctl.
The first one in the series is a fix for minor bogosity, the rest -
cleanups. Elimination of more d_alloc_name() call sites on conversions
to simple_start_creating() is what got that into preparation parts of
tree-in-dcache...
Branch in -rc5-based, lives in
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git #work.nfsctl
individual patches in followups. If nobody objects, into -next it goes...
Shortlog:
nfsctl: symlink has no business bumping link count of parent directory
nfsd_mkdir(): switch to simple_start_creating()
_nfsd_symlink(): switch to simple_start_creating()
nfsdfs_create_files(): switch to simple_start_creating()
nfsd_get_inode(): lift setting ->i_{,f}op to callers.
Diffstat:
fs/nfsd/nfsctl.c | 137 ++++++++++++++++++++-----------------------------------
1 file changed, 49 insertions(+), 88 deletions(-)
next reply other threads:[~2025-09-11 22:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 22:44 Al Viro [this message]
2025-09-11 22:46 ` [PATCH 1/5] nfsctl: symlink has no business bumping link count of parent directory Al Viro
2025-09-11 22:46 ` [PATCH 2/5] nfsd_mkdir(): switch to simple_start_creating() Al Viro
2025-09-11 22:46 ` [PATCH 3/5] _nfsd_symlink(): " Al Viro
2025-09-11 22:46 ` [PATCH 4/5] nfsdfs_create_files(): " Al Viro
2025-09-11 23:20 ` NeilBrown
2025-09-11 22:46 ` [PATCH 5/5] nfsd_get_inode(): lift setting ->i_{,f}op to callers Al Viro
2025-09-11 23:20 ` [PATCHES] nfsctl fix and cleanups NeilBrown
2025-09-12 11:38 ` Jeff Layton
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=20250911224429.GX39973@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
/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