From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL 12/12 for v6.18] async directory preliminaries
Date: Fri, 26 Sep 2025 16:19:06 +0200 [thread overview]
Message-ID: <20250926-vfs-async-920f57c61768@brauner> (raw)
In-Reply-To: <20250926-vfs-618-e880cf3b910f@brauner>
Hey Linus,
/* Summary */
This contains further preparatory changes for the asynchronous directory
locking scheme:
* Add lookup_one_positive_killable() which allows overlayfs to perform
lookup that won't block on a fatal signal.
* Unify the mount idmap handling in struct renamedata as a rename can
only happen within a single mount.
* Introduce kern_path_parent() for audit which sets the path to the
parent and returns a dentry for the target without holding any locks
on return.
* Rename kern_path_locked() as it is only used to prepare for the
removal of an object from the filesystem:
kern_path_locked() => start_removing_path()
kern_path_create() => start_creating_path()
user_path_create() => start_creating_user_path()
user_path_locked_at() => start_removing_user_path_at()
done_path_create() => end_creating_path()
NA => end_removing_path()
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3+b1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
[1] https://lore.kernel.org/linux-next/aNOyrz1bd1WTrZgc@finisterre.sirena.org.uk
[2] https://lore.kernel.org/linux-next/aNU3FtEZ3w_NcYwI@sirena.org.uk
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.18-rc1.async
for you to fetch changes up to 4f5ea5aa0dcdd3c7487fbabad5b86b3cd7d2b8c4:
Merge patch series "vfs: preparatory changes to centralize locking of create/remove/rename" (2025-09-23 12:37:42 +0200)
Please consider pulling these changes from the signed vfs-6.18-rc1.async tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.18-rc1.async
----------------------------------------------------------------
Christian Brauner (1):
Merge patch series "vfs: preparatory changes to centralize locking of create/remove/rename"
NeilBrown (6):
VFS/ovl: add lookup_one_positive_killable()
VFS: discard err2 in filename_create()
VFS: unify old_mnt_idmap and new_mnt_idmap in renamedata
VFS/audit: introduce kern_path_parent() for audit
VFS: rename kern_path_locked() and related functions.
debugfs: rename start_creating() to debugfs_start_creating()
Documentation/filesystems/porting.rst | 12 ++
arch/powerpc/platforms/cell/spufs/syscalls.c | 4 +-
drivers/base/devtmpfs.c | 22 ++--
fs/bcachefs/fs-ioctl.c | 10 +-
fs/cachefiles/namei.c | 3 +-
fs/debugfs/inode.c | 11 +-
fs/ecryptfs/inode.c | 3 +-
fs/init.c | 17 +--
fs/namei.c | 164 ++++++++++++++++++++-------
fs/nfsd/vfs.c | 3 +-
fs/ocfs2/refcounttree.c | 4 +-
fs/overlayfs/overlayfs.h | 3 +-
fs/overlayfs/readdir.c | 28 ++---
fs/smb/server/vfs.c | 11 +-
include/linux/fs.h | 6 +-
include/linux/namei.h | 21 ++--
kernel/audit_fsnotify.c | 11 +-
kernel/audit_watch.c | 3 +-
kernel/bpf/inode.c | 4 +-
net/unix/af_unix.c | 6 +-
20 files changed, 216 insertions(+), 130 deletions(-)
next prev parent reply other threads:[~2025-09-26 14:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 14:18 [GIT PULL 00/12 for v6.18] vfs 6.18 Christian Brauner
2025-09-26 14:18 ` [GIT PULL 01/12 for v6.18] misc Christian Brauner
2025-09-29 9:47 ` Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 02/12 for v6.18] mount Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 03/12 for v6.18] inode Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 04/12 for v6.18] iomap Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 05/12 for v6.18] pidfs Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-10-01 14:18 ` Oleg Nesterov
2025-10-06 13:48 ` Christian Brauner
2025-10-07 14:34 ` Oleg Nesterov
2025-10-10 11:00 ` Christian Brauner
2025-09-26 14:19 ` [GIT PULL 06/12 for v6.18] rust Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 07/12 for v6.18] workqueue Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 08/12 for v6.18] core kernel Christian Brauner
2025-09-27 12:19 ` Sasha Levin
2025-09-29 9:53 ` Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 9/12 for v6.18] afs Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 10/12 for v6.18] namespaces Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 11/12 for v6.18] writeback Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` Christian Brauner [this message]
2025-09-29 19:31 ` [GIT PULL 12/12 for v6.18] async directory preliminaries 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=20250926-vfs-async-920f57c61768@brauner \
--to=brauner@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).