VFS: more prep for change to directory locking
From: | NeilBrown <neilb-AT-ownmail.net> | |
To: | "Alexander Viro" <viro-AT-zeniv.linux.org.uk>, "Christian Brauner" <brauner-AT-kernel.org>, "Amir Goldstein" <amir73il-AT-gmail.com>, Jeff Layton <jlayton-AT-kernel.org> | |
Subject: | [PATCH v3 0/6] VFS: more prep for change to directory locking | |
Date: | Mon, 15 Sep 2025 12:13:40 +1000 | |
Message-ID: | <20250915021504.2632889-1-neilb@ownmail.net> | |
Cc: | "Jan Kara" <jack-AT-suse.cz>, linux-fsdevel-AT-vger.kernel.org | |
Archive-link: | Article |
This is a re-revised selection of cleanups and API renaming which continues my work to centralise locking of create/remove/rename operations. I've dropped the simple_end_creating etc changes which conflict with some of Al's work, I've added a note to the first patch explaining that the linked list does not need locking, and I've added a patch to rename start_creating() in debugfs so the name can be used elsewhere in later patches. Thanks, NeilBrown [PATCH v3 1/6] VFS/ovl: add lookup_one_positive_killable() [PATCH v3 2/6] VFS: discard err2 in filename_create() [PATCH v3 3/6] VFS: unify old_mnt_idmap and new_mnt_idmap in [PATCH v3 4/6] VFS/audit: introduce kern_path_parent() for audit [PATCH v3 5/6] VFS: rename kern_path_locked() and related functions. [PATCH v3 6/6] debugfs: rename start_creating() to debugfs_start_creating()