All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, Christian Brauner <brauner@kernel.org>
Subject: [git pull] pile 3: nfsctl
Date: Thu, 2 Oct 2025 07:00:50 +0100	[thread overview]
Message-ID: <20251002060050.GI39973@ZenIV> (raw)

More stuff pulled from tree-in-dcache series - nfsctl this time.  Similar
to rpcpipefs and securityfs piles last cycle...

The following changes since commit 76eeb9b8de9880ca38696b2fb56ac45ac0a25c6c:

  Linux 6.17-rc5 (2025-09-07 14:22:57 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-nfsctl

for you to fetch changes up to 92003056e5d45f0f32a87f9f96d15902f2f21fbf:

  nfsd_get_inode(): lift setting ->i_{,f}op to callers. (2025-09-17 19:40:40 -0400)

----------------------------------------------------------------
nfsctl cleanups and a fix

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

----------------------------------------------------------------
Al Viro (5):
      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.

 fs/nfsd/nfsctl.c | 137 ++++++++++++++++++++-----------------------------------
 1 file changed, 49 insertions(+), 88 deletions(-)

             reply	other threads:[~2025-10-02  6:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02  6:00 Al Viro [this message]
2025-10-03 18:41 ` [git pull] pile 3: nfsctl 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=20251002060050.GI39973@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@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.