summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/extent_io.c
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@suse.com>2024-04-16 15:19:03 +0100
committerDavid Sterba <dsterba@suse.com>2024-05-07 21:31:07 +0200
commit433a3e01dda1d463159a9620b40ba027514f0ea5 (patch)
treee68d1b7d900c5191b1de5d1b6fc8ff1a3c5f76fb /fs/btrfs/extent_io.c
parent85d288309ab5463140a2d00b3827262fb14e7db4 (diff)
downloadlinux-433a3e01dda1d463159a9620b40ba027514f0ea5.tar.gz
linux-433a3e01dda1d463159a9620b40ba027514f0ea5.tar.bz2
linux-433a3e01dda1d463159a9620b40ba027514f0ea5.zip
btrfs: remove i_size restriction at try_release_extent_mapping()
Currently we don't attempt to release extent maps if the inode has an i_size that is not greater than 16M. This condition was added way back in 2008 by commit 70dec8079d78 ("Btrfs: extent_io and extent_state optimizations"), without any explanation about it. A quick chat with Chris on slack revealed that the goal was probably to release the extent maps for small files only when closing the inode. This however can be harmful in case we have tons of such files being kept open for very long periods of time, since we will consume more and more pages for extent maps. So remove the condition. Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Signed-off-by: Filipe Manana <fdmanana@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/extent_io.c')
-rw-r--r--fs/btrfs/extent_io.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
index f689c53553e3..ff9132b897e3 100644
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -2402,8 +2402,7 @@ int try_release_extent_mapping(struct page *page, gfp_t mask)
struct extent_io_tree *io_tree = &inode->io_tree;
struct extent_map_tree *extent_tree = &inode->extent_tree;
- if (gfpflags_allow_blocking(mask) &&
- page->mapping->host->i_size > SZ_16M) {
+ if (gfpflags_allow_blocking(mask)) {
u64 len;
while (start <= end) {
const u64 cur_gen = btrfs_get_fs_generation(inode->root->fs_info);