diff options
author | Josef Bacik <jbacik@fusionio.com> | 2013-10-07 22:11:09 -0400 |
---|---|---|
committer | Chris Mason <chris.mason@fusionio.com> | 2013-10-10 21:27:56 -0400 |
commit | 7bf811a595a895b7a886dcf218d0d34f97df76dc (patch) | |
tree | 84ac740c10a366b012a3b5f0a4551fe944fbf1d1 /kernel/relay.c | |
parent | 4871c1588f92c6c13f4713a7009f25f217055807 (diff) |
Btrfs: limit delalloc pages outside of find_delalloc_range
Liu fixed part of this problem and unfortunately I steered him in slightly the
wrong direction and so didn't completely fix the problem. The problem is we
limit the size of the delalloc range we are looking for to max bytes and then we
try to lock that range. If we fail to lock the pages in that range we will
shrink the max bytes to a single page and re loop. However if our first page is
inside of the delalloc range then we will end up limiting the end of the range
to a period before our first page. This is illustrated below
[0 -------- delalloc range --------- 256mb]
[page]
So find_delalloc_range will return with delalloc_start as 0 and end as 128mb,
and then we will notice that delalloc_start < *start and adjust it up, but not
adjust delalloc_end up, so things go sideways. To fix this we need to not limit
the max bytes in find_delalloc_range, but in find_lock_delalloc_range and that
way we don't end up with this confusion. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
Diffstat (limited to 'kernel/relay.c')
0 files changed, 0 insertions, 0 deletions