From: Li Zefan <lizf@cn.fujitsu.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Cc: lidongyang@novell.com
Subject: [PATCH 1/2] Btrfs: fix space leak when skipping small extents during trimming
Date: Tue, 21 Jun 2011 13:49:19 +0800 [thread overview]
Message-ID: <4E0030DF.4080704@cn.fujitsu.com> (raw)
We're taking a free space extent out of the free space cache, trimming
it and then putting it back into the cache.
However for an extent that is smaller than the specified minimum length,
it's taken out but won't be put back, which causes space leak.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
---
Unfortunately I have no trim-able device to test the patch.
---
fs/btrfs/free-space-cache.c | 34 +++++++++++++++++-----------------
1 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/fs/btrfs/free-space-cache.c b/fs/btrfs/free-space-cache.c
index 9f985a4..292c0d9 100644
--- a/fs/btrfs/free-space-cache.c
+++ b/fs/btrfs/free-space-cache.c
@@ -2460,6 +2460,7 @@ int btrfs_trim_block_group(struct btrfs_block_group_cache *block_group,
u64 bytes = 0;
u64 actually_trimmed;
int ret = 0;
+ int update_ret;
*trimmed = 0;
@@ -2483,6 +2484,7 @@ int btrfs_trim_block_group(struct btrfs_block_group_cache *block_group,
}
if (entry->bitmap) {
+ bytes = 0;
ret = search_bitmap(ctl, entry, &start, &bytes);
if (!ret) {
if (start >= end) {
@@ -2490,6 +2492,8 @@ int btrfs_trim_block_group(struct btrfs_block_group_cache *block_group,
break;
}
bytes = min(bytes, end - start);
+ if (bytes < minlen)
+ goto next;
bitmap_clear_bits(ctl, entry, start, bytes);
if (entry->bytes == 0)
free_bitmap(ctl, entry);
@@ -2503,33 +2507,29 @@ int btrfs_trim_block_group(struct btrfs_block_group_cache *block_group,
} else {
start = entry->offset;
bytes = min(entry->bytes, end - start);
+ if (bytes < minlen)
+ goto next;
unlink_free_space(ctl, entry);
kmem_cache_free(btrfs_free_space_cachep, entry);
}
spin_unlock(&ctl->tree_lock);
- if (bytes >= minlen) {
- int update_ret;
- update_ret = btrfs_update_reserved_bytes(block_group,
- bytes, 1, 1);
+ update_ret = btrfs_update_reserved_bytes(block_group,
+ bytes, 1, 1);
- ret = btrfs_error_discard_extent(fs_info->extent_root,
- start,
- bytes,
- &actually_trimmed);
+ ret = btrfs_error_discard_extent(fs_info->extent_root, start,
+ bytes, &actually_trimmed);
- btrfs_add_free_space(block_group, start, bytes);
- if (!update_ret)
- btrfs_update_reserved_bytes(block_group,
- bytes, 0, 1);
+ btrfs_add_free_space(block_group, start, bytes);
+ if (!update_ret)
+ btrfs_update_reserved_bytes(block_group, bytes, 0, 1);
- if (ret)
- break;
- *trimmed += actually_trimmed;
- }
+ if (ret)
+ break;
+ *trimmed += actually_trimmed;
+next:
start += bytes;
- bytes = 0;
if (fatal_signal_pending(current)) {
ret = -ERESTARTSYS;
next reply other threads:[~2011-06-21 5:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 5:49 Li Zefan [this message]
2011-06-21 5:50 ` [PATCH 2/2] Btrfs: fix space leak when trimming free extents Li Zefan
2011-06-21 9:45 ` Li Dongyang
2011-07-05 4:07 ` [PATCH 1/2] Btrfs: fix space leak when skipping small extents during trimming Li Dongyang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E0030DF.4080704@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=lidongyang@novell.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).