diff options
author | NeilBrown <neil@brown.name> | 2025-09-22 14:29:52 +1000 |
---|---|---|
committer | Christian Brauner <brauner@kernel.org> | 2025-09-23 12:37:36 +0200 |
commit | 3d18f80ce181ba27f37d0ec1c550b22acb01dd49 (patch) | |
tree | 09964e812e5b4716ae9b8cbf75d2f548d61bae9e /scripts/kernel-doc.py | |
parent | 76a53de6f7ff0641570364234fb4489f4d4fc8e9 (diff) |
VFS: rename kern_path_locked() and related functions.
kern_path_locked() is now only used to prepare for removing an object
from the filesystem (and that is the only credible reason for wanting a
positive locked dentry). Thus it corresponds to kern_path_create() and
so should have a corresponding name.
Unfortunately the name "kern_path_create" is somewhat misleading as it
doesn't actually create anything. The recently added
simple_start_creating() provides a better pattern I believe. The
"start" can be matched with "end" to bracket the creating or removing.
So this patch changes names:
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
and also introduces end_removing_path() which is identical to
end_creating_path().
__start_removing_path (which was __kern_path_locked) is enhanced to
call mnt_want_write() for consistency with the start_creating_path().
Reviewed-by: Amir Goldstein <amir73il@gmail.com>
Signed-off-by: NeilBrown <neil@brown.name>
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'scripts/kernel-doc.py')
0 files changed, 0 insertions, 0 deletions