From: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz
Subject: [PATCH 1/2] btrfs: use correct offset for reloc_inode in prealloc_file_extent_cluster()
Date: Wed, 6 Jul 2016 18:37:52 +0800 [thread overview]
Message-ID: <20160706103753.4908-1-wangxg.fnst@cn.fujitsu.com> (raw)
In prealloc_file_extent_cluster(), btrfs_check_data_free_space() uses
wrong file offset for reloc_inode, it uses cluster->start and cluster->end,
which indeed are extent's bytenr. The correct value should be
cluster->[start|end] minus block group's start bytenr.
start bytenr cluster->start
| | extent | extent | ...| extent |
|----------------------------------------------------------------|
| block group reloc_inode |
Signed-off-by: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
---
fs/btrfs/relocation.c | 27 +++++++++++++++------------
1 file changed, 15 insertions(+), 12 deletions(-)
diff --git a/fs/btrfs/relocation.c b/fs/btrfs/relocation.c
index 0477dca..abc2f69 100644
--- a/fs/btrfs/relocation.c
+++ b/fs/btrfs/relocation.c
@@ -3030,34 +3030,37 @@ int prealloc_file_extent_cluster(struct inode *inode,
u64 num_bytes;
int nr = 0;
int ret = 0;
+ u64 prealloc_start, prealloc_end;
BUG_ON(cluster->start != cluster->boundary[0]);
inode_lock(inode);
- ret = btrfs_check_data_free_space(inode, cluster->start,
- cluster->end + 1 - cluster->start);
+ start = cluster->start - offset;
+ end = cluster->end - offset;
+ ret = btrfs_check_data_free_space(inode, start, end + 1 - start);
if (ret)
goto out;
while (nr < cluster->nr) {
- start = cluster->boundary[nr] - offset;
+ prealloc_start = cluster->boundary[nr] - offset;
if (nr + 1 < cluster->nr)
- end = cluster->boundary[nr + 1] - 1 - offset;
+ prealloc_end = cluster->boundary[nr + 1] - 1 - offset;
else
- end = cluster->end - offset;
+ prealloc_end = cluster->end - offset;
- lock_extent(&BTRFS_I(inode)->io_tree, start, end);
- num_bytes = end + 1 - start;
- ret = btrfs_prealloc_file_range(inode, 0, start,
+ lock_extent(&BTRFS_I(inode)->io_tree, prealloc_start,
+ prealloc_end);
+ num_bytes = prealloc_end + 1 - prealloc_start;
+ ret = btrfs_prealloc_file_range(inode, 0, prealloc_start,
num_bytes, num_bytes,
- end + 1, &alloc_hint);
- unlock_extent(&BTRFS_I(inode)->io_tree, start, end);
+ prealloc_end + 1, &alloc_hint);
+ unlock_extent(&BTRFS_I(inode)->io_tree, prealloc_start,
+ prealloc_end);
if (ret)
break;
nr++;
}
- btrfs_free_reserved_data_space(inode, cluster->start,
- cluster->end + 1 - cluster->start);
+ btrfs_free_reserved_data_space(inode, start, end + 1 - start);
out:
inode_unlock(inode);
return ret;
--
2.9.0
next reply other threads:[~2016-07-06 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 10:37 Wang Xiaoguang [this message]
2016-07-06 10:37 ` [PATCH 2/2] btrfs: fix false ENOSPC for btrfs_fallocate() Wang Xiaoguang
2016-07-06 12:27 ` Holger Hoffstätte
2016-07-07 2:27 ` Wang Xiaoguang
2016-07-11 11:34 ` Wang Xiaoguang
2016-07-06 19:54 ` [PATCH 1/2] btrfs: use correct offset for reloc_inode in prealloc_file_extent_cluster() Liu Bo
2016-07-07 2:26 ` Wang Xiaoguang
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=20160706103753.4908-1-wangxg.fnst@cn.fujitsu.com \
--to=wangxg.fnst@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--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).