diff options
| author | Josef Bacik <josef@toxicpanda.com> | 2020-11-06 16:27:32 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-01-09 13:25:05 +0100 |
| commit | 51b03b7473a0d9dc4bc05ffed6c2c34fff26dc35 (patch) | |
| tree | 67bfdb9f5935a0956111ba66445bf0c401bf7cf8 /fs/proc/array.c | |
| parent | 20d96aa61607a65fd077dc0679ef9bdd19802b9d (diff) | |
btrfs: locking: remove the recursion handling code
[ Upstream commit 4048daedb910f83f080c6bb03c78af794aebdff5 ]
Now that we're no longer using recursion, rip out all of the supporting
code. Follow up patches will clean up the callers of these functions.
The extent_buffer::lock_owner is still retained as it allows safety
checks in btrfs_init_new_buffer for the case that the free space cache
is corrupted and we try to allocate a block that we are currently using
and have locked in the path.
Reviewed-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Stable-dep-of: 97e86631bccd ("btrfs: don't set lock_owner when locking extent buffer for reading")
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'fs/proc/array.c')
0 files changed, 0 insertions, 0 deletions