- 05 Feb, 2024 40 commits
-
-
Jeff Layton authored
Add a new struct file_lease and move the lease-specific fields from struct file_lock to it. Convert the appropriate API calls to take struct file_lease instead, and convert the callers to use them. There is zero overlap between the lock manager operations for file locks and the ones for file leases, so split the lease-related operations off into a new lease_manager_operations struct. Signed-off-by:
Jeff Layton <jlayton@kernel.org> Link: https://lore.kernel.org/r/20240131-flsplit-v3-47-c6129007ee8d@kernel.orgReviewed-by:
NeilBrown <neilb@suse.de> Signed-off-by:
Christian Brauner <brauner@kernel.org>
-
Jeff Layton authored
Everything has been converted to access fl_core fields directly, so we can now drop these. Signed-off-by:
-
Jeff Layton authored
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:
-
Jeff Layton authored
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:
-
Jeff Layton authored
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:
-
Jeff Layton authored
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:
-
Jeff Layton authored
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:
-
Jeff Layton authored
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:
-
Jeff Layton authored
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:
-
Jeff Layton authored
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:
-
Jeff Layton authored
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:
-
Jeff Layton authored
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:
-
Jeff Layton authored
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:
-
Jeff Layton authored
Most of the existing APIs have remained the same, but subsystems that access file_lock fields directly need to reach into struct file_lock_core now. Signed-off-by:
-
Jeff Layton authored
Reduce some pointer manipulation by just using file_lock_core where we can and only translate to a file_lock when needed. Signed-off-by:
-
Jeff Layton authored
locks_translate_pid is used on both locks and leases, so have that take struct file_lock_core. Signed-off-by:
-
Jeff Layton authored
Have these functions take a file_lock_core pointer instead of a file_lock. Signed-off-by:
-
Jeff Layton authored
Have locks_wake_up_blocks take a file_lock_core pointer, and fix up the callers to pass one in. Signed-off-by:
-
Jeff Layton authored
Have assign_type take struct file_lock_core instead of file_lock. Signed-off-by:
-
Jeff Layton authored
Rename the old __locks_delete_block to __locks_unlink_lock. Rename change old locks_delete_block function to __locks_delete_block and have it take a file_lock_core. Make locks_delete_block a simple wrapper around __locks_delete_block. Also, change __locks_insert_block to take struct file_lock_core, and fix up its callers. Signed-off-by:
-
Jeff Layton authored
Rework the internals of locks_delete_block to use struct file_lock_core (mostly just for clarity's sake). The prototype is not changed. Signed-off-by:
-
Jeff Layton authored
Both locks and leases deal with fl_blocker. Switch the fl_blocker pointer in struct file_lock_core to point to the file_lock_core of the blocker instead of a file_lock structure. Signed-off-by:
-
Jeff Layton authored
Have both __locks_insert_block and the deadlock and conflict checking functions take a struct file_lock_core pointer instead of a struct file_lock one. Also, change posix_locks_deadlock to return bool. Signed-off-by:
-
Jeff Layton authored
Convert __locks_delete_block and __locks_wake_up_blocks to take a struct file_lock_core pointer. While we could do this in another way, we're going to need to add a file_lock() helper function later anyway, so introduce and use it now. Signed-off-by:
-
Jeff Layton authored
Have locks_insert_global_blocked and locks_delete_global_blocked take a struct file_lock_core pointer. Signed-off-by:
-
Jeff Layton authored
Convert these functions to take a file_lock_core instead of a file_lock. Signed-off-by:
-
Jeff Layton authored
Convert posix_owner_key to take struct file_lock_core pointer, and fix up the callers to pass one in. Signed-off-by:
-
Jeff Layton authored
Change posix_same_owner to take struct file_lock_core pointers, and convert the callers to pass those in. Signed-off-by:
-
Jeff Layton authored
Convert more internal fs/locks.c functions to take and deal with struct file_lock_core instead of struct file_lock: - locks_dump_ctx_list - locks_check_ctx_file_list - locks_release_private - locks_owner_has_blockers Signed-off-by:
-
Jeff Layton authored
Convert fs/locks.c to access fl_core fields direcly rather than using the backward-compatibility macros. Most of this was done with coccinelle, with a few by-hand fixups. Signed-off-by:
-
Jeff Layton authored
In a future patch, we're going to split file leases into their own structure. Since a lot of the underlying machinery uses the same fields move those into a new file_lock_core, and embed that inside struct file_lock. For now, add some macros to ensure that we can continue to build while the conversion is in progress. Signed-off-by:
-
Jeff Layton authored
These don't add a lot of value over just open-coding the flag check. Suggested-by:
-
Jeff Layton authored
Convert to using the new file locking helper functions. Signed-off-by:
-
Jeff Layton authored
Convert to using the new file locking helper functions. Signed-off-by:
-
Jeff Layton authored
Convert to using the new file locking helper functions. Signed-off-by:
-
Jeff Layton authored
Convert to using the new file locking helper functions. Also, in later patches we're going to introduce some macros with names that clash with the variable names in nfsd4_lock. Rename them. Signed-off-by:
-
Jeff Layton authored
Convert to using the new file locking helper functions. Also, in later patches we're going to introduce some temporary macros with names that clash with the variable name in nfs4_proc_unlck. Rename it. Signed-off-by:
-
Jeff Layton authored
Convert to using the new file locking helper functions. Also in later patches we're going to introduce some macros with names that clash with the variable names in nlmclnt_lock. Rename them. Signed-off-by:
-
Jeff Layton authored
Convert to using the new file locking helper functions. Signed-off-by:
-
Jeff Layton authored
Convert to using the new file locking helper functions. Also, in later patches we're going to introduce some temporary macros with names that clash with the variable name in dlm_posix_unlock. Rename it. Signed-off-by:
-
