diff options
| author | Christoph Hellwig <hch@lst.de> | 2023-05-08 07:58:39 -0700 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2023-06-19 13:59:26 +0200 |
| commit | f880fe6e0b4b127d6e2a007fe68bdf5651677ae2 (patch) | |
| tree | 42426dc35351c19d8e0fac9de2e0beb16a8d62d3 /fs/btrfs/extent_io.h | |
| parent | f18cc97845aa4ae0e795c088c979fe1642b3b8e5 (diff) | |
| download | linux-f880fe6e0b4b127d6e2a007fe68bdf5651677ae2.tar.gz linux-f880fe6e0b4b127d6e2a007fe68bdf5651677ae2.tar.bz2 linux-f880fe6e0b4b127d6e2a007fe68bdf5651677ae2.zip | |
btrfs: don't hold an extra reference for redirtied buffers
When btrfs_redirty_list_add redirties a buffer, it also acquires
an extra reference that is released on transaction commit. But
this is not required as buffers that are dirty or under writeback
are never freed (look for calls to extent_buffer_under_io())).
Remove the extra reference and the infrastructure used to drop it
again.
History behind redirty logic:
In the first place, it used releasing_list to hold all the
to-be-released extent buffers, and decided which buffers to re-dirty at
the commit time. Then, in a later version, the behaviour got changed to
re-dirty a necessary buffer and add re-dirtied one to the list in
btrfs_free_tree_block(). In short, the list was there mostly for the
patch series' historical reason.
Reviewed-by: Naohiro Aota <naohiro.aota@wdc.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
[ add Naohiro's comment regarding history ]
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/extent_io.h')
| -rw-r--r-- | fs/btrfs/extent_io.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/fs/btrfs/extent_io.h b/fs/btrfs/extent_io.h index f937654230d3..6f3cfadd232c 100644 --- a/fs/btrfs/extent_io.h +++ b/fs/btrfs/extent_io.h @@ -89,7 +89,6 @@ struct extent_buffer { struct rw_semaphore lock; struct page *pages[INLINE_EXTENT_BUFFER_PAGES]; - struct list_head release_list; #ifdef CONFIG_BTRFS_DEBUG struct list_head leak_list; #endif |