Linux filesystem development
 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][6.17] vfs.git 3/9: rpc_pipefs
Date: Sat, 26 Jul 2025 09:03:26 +0100	[thread overview]
Message-ID: <20250726080326.GB1456602@ZenIV> (raw)
In-Reply-To: <20250726080119.GA222315@ZenIV>

[the first couple of commits is shared with #work.simple_recursive_removal]

The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:

  Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 350db61fbeb940502a16e74153ee5954d03622e9:

  rpc_create_client_dir(): return 0 or -E... (2025-07-02 22:44:55 -0400)

----------------------------------------------------------------
Massage rpc_pipefs to use saner primitives and clean up the
APIs provided to the rest of the kernel.

----------------------------------------------------------------
Al Viro (18):
      simple_recursive_removal(): saner interaction with fsnotify
      better lockdep annotations for simple_recursive_removal()
      new helper: simple_start_creating()
      rpc_pipe: clean failure exits in fill_super
      rpc_{rmdir_,}depopulate(): use simple_recursive_removal() instead
      rpc_unlink(): use simple_recursive_removal()
      rpc_populate(): lift cleanup into callers
      rpc_unlink(): saner calling conventions
      rpc_mkpipe_dentry(): saner calling conventions
      rpc_pipe: don't overdo directory locking
      rpc_pipe: saner primitive for creating subdirectories
      rpc_pipe: saner primitive for creating regular files
      rpc_mkpipe_dentry(): switch to simple_start_creating()
      rpc_gssd_dummy_populate(): don't bother with rpc_populate()
      rpc_pipe: expand the calls of rpc_mkdir_populate()
      rpc_new_dir(): the last argument is always NULL
      rpc_create_client_dir(): don't bother with rpc_populate()
      rpc_create_client_dir(): return 0 or -E...

 fs/debugfs/inode.c                 |  21 +-
 fs/libfs.c                         |  34 ++-
 fs/nfs/blocklayout/rpc_pipefs.c    |  53 ++--
 fs/nfs/nfs4idmap.c                 |  14 +-
 fs/nfsd/nfs4recover.c              |  49 ++--
 fs/tracefs/inode.c                 |  15 +-
 include/linux/fs.h                 |   1 +
 include/linux/sunrpc/rpc_pipe_fs.h |   6 +-
 net/sunrpc/auth_gss/auth_gss.c     |  13 +-
 net/sunrpc/clnt.c                  |  36 +--
 net/sunrpc/rpc_pipe.c              | 530 ++++++++++---------------------------
 11 files changed, 230 insertions(+), 542 deletions(-)

  parent reply	other threads:[~2025-07-26  8:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-26  8:01 [git pull][6.17] vfs.git 1/9: d_flags pile Al Viro
2025-07-26  8:02 ` [git pull][6.17] vfs.git 2/9: simple_recursive_removal Al Viro
2025-07-28 23:41   ` pr-tracker-bot
2025-07-26  8:03 ` Al Viro [this message]
2025-07-28 23:41   ` [git pull][6.17] vfs.git 3/9: rpc_pipefs pr-tracker-bot
2025-07-26  8:04 ` [git pull][6.17] vfs.git 4/9: asm/param.h pile Al Viro
2025-07-28 23:41   ` pr-tracker-bot
2025-07-26  8:05 ` [git pull][6.17] vfs.git 5/9: securityfs Al Viro
2025-07-28 23:41   ` pr-tracker-bot
2025-07-26  8:05 ` [git pull][6.17] vfs.git 6/9: misc pile Al Viro
2025-07-28 23:41   ` pr-tracker-bot
2025-07-26  8:08 ` [git pull][6.17] vfs.git 7/9: ceph d_name fixes Al Viro
2025-07-28 23:41   ` pr-tracker-bot
2025-07-26  8:08 ` [git pull][6.17] vfs.git 8/9: CLASS(fd) followup Al Viro
2025-07-28 23:41   ` pr-tracker-bot
2025-07-26  8:09 ` [git pull][6.17] vfs.git 9/9: mount pile Al Viro
2025-07-28 23:41   ` pr-tracker-bot
2025-07-28 23:41 ` [git pull][6.17] vfs.git 1/9: d_flags pile 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=20250726080326.GB1456602@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox