From: NeilBrown <neilb@ownmail.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Jeff Layton <jlayton@kernel.org>,
Amir Goldstein <amir73il@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/7]] VFS: Prepare to lift lookup out of exclusive lock for directory ops
Date: Thu, 30 Apr 2026 11:56:53 +1000 [thread overview]
Message-ID: <20260430020137.3305302-1-neilb@ownmail.net> (raw)
Following are 7 VFS patches which modify or introduce APIs that will
allow modifying filesystems so that they will work with a proposed
change to move d_alloc_paralle() out from the parent i_rw_sem lock.
If these can land in a non-rebasing tree, I can work with individual
filesystem maintainers to start using these APIs.
I haven't included d_alloc_noblock_return() as it is only needed for one
fs (ovl) and it is not yet clear that it is the best approach.
I also haven't included the change to d_alloc_name() as that is only
needed so that I can deprecate d_alloc() and there is no rush for that.
Patch 2/7 is exactly the patch Al proposed in the conversation for v3.
I have taken the libery to added a Signed-off-by by Al to match the
Co-developed-by. I hope that was not inappropriate.
I have been testing this series over NFS mounts from XFS so patches 2
and 3 don't seem to be causing any problems. The changes in 4/5/6/7
won't be tested by this, and some cannot be tested until filesystems
start using new interfaces.
Thanks,
NeilBrown
[PATCH v4 1/7] VFS: fix various typos in documentation for
[PATCH v4 2/7] VFS: use wait_var_event for waiting in
[PATCH v4 3/7] VFS: enhance d_splice_alias() to handle in-lookup
[PATCH v4 4/7] VFS: introduce d_alloc_noblock()
[PATCH v4 5/7] VFS: add d_duplicate()
[PATCH v4 6/7] VFS: Add LOOKUP_SHARED flag.
[PATCH v4 7/7] VFS/xfs/ntfs: drop parent lock across
next reply other threads:[~2026-04-30 3:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 1:56 NeilBrown [this message]
2026-04-30 1:56 ` [PATCH v4 1/7] VFS: fix various typos in documentation for start_creating start_removing etc NeilBrown
2026-04-30 1:56 ` [PATCH v4 2/7] VFS: use wait_var_event for waiting in d_alloc_parallel() NeilBrown
2026-05-11 18:01 ` Jeff Layton
2026-05-11 21:58 ` NeilBrown
2026-04-30 1:56 ` [PATCH v4 3/7] VFS: enhance d_splice_alias() to handle in-lookup dentries NeilBrown
2026-04-30 1:56 ` [PATCH v4 4/7] VFS: introduce d_alloc_noblock() NeilBrown
2026-04-30 1:56 ` [PATCH v4 5/7] VFS: add d_duplicate() NeilBrown
2026-04-30 1:56 ` [PATCH v4 6/7] VFS: Add LOOKUP_SHARED flag NeilBrown
2026-04-30 1:57 ` [PATCH v4 7/7] VFS/xfs/ntfs: drop parent lock across d_alloc_parallel() in d_add_ci() NeilBrown
2026-04-30 2:03 [PATCH v4 0/7]] VFS: Prepare to lift lookup out of exclusive lock for directory ops NeilBrown
2026-04-30 7:50 ` Jeff Layton
2026-04-30 9:08 ` NeilBrown
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=20260430020137.3305302-1-neilb@ownmail.net \
--to=neilb@ownmail.net \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®