mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-08-27 11:19:37 +00:00
btrfs: don't clear page extent mapped if we're not invalidating the full page
[BUG] With current btrfs subpage rw support, the following script can lead to fs hang: $ mkfs.btrfs -f -s 4k $dev $ mount $dev -o nospace_cache $mnt $ fsstress -w -n 100 -p 1 -s 1608140256 -v -d $mnt The fs will hang at btrfs_start_ordered_extent(). [CAUSE] In above test case, btrfs_invalidate() will be called with the following parameters: offset = 0 length = 53248 page dirty = 1 subpage dirty bitmap = 0x2000 Since @offset is 0, btrfs_invalidate() will try to invalidate the full page, and finally call clear_page_extent_mapped() which will detach subpage structure from the page. And since the page no longer has subpage structure, the subpage dirty bitmap will be cleared, preventing the dirty range from being written back, thus no way to wake up the ordered extent. [FIX] Just follow other filesystems, only to invalidate the page if the range covers the full page. There are cases like truncate_setsize() which can call btrfs_invalidatepage() with offset == 0 and length != 0 for the last page of an inode. Although the old code will still try to invalidate the full page, we are still safe to just wait for ordered extent to finish. So it shouldn't cause extra problems. Tested-by: Ritesh Harjani <riteshh@linux.ibm.com> # [ppc64] Tested-by: Anand Jain <anand.jain@oracle.com> # [aarch64] Signed-off-by: Qu Wenruo <wqu@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
parent
0528476b6a
commit
bcd77455d5
1 changed files with 13 additions and 1 deletions
|
@ -8381,7 +8381,19 @@ static void btrfs_invalidatepage(struct page *page, unsigned int offset,
|
|||
*/
|
||||
wait_on_page_writeback(page);
|
||||
|
||||
if (offset) {
|
||||
/*
|
||||
* For subpage case, we have call sites like
|
||||
* btrfs_punch_hole_lock_range() which passes range not aligned to
|
||||
* sectorsize.
|
||||
* If the range doesn't cover the full page, we don't need to and
|
||||
* shouldn't clear page extent mapped, as page->private can still
|
||||
* record subpage dirty bits for other part of the range.
|
||||
*
|
||||
* For cases that can invalidate the full even the range doesn't
|
||||
* cover the full page, like invalidating the last page, we're
|
||||
* still safe to wait for ordered extent to finish.
|
||||
*/
|
||||
if (!(offset == 0 && length == PAGE_SIZE)) {
|
||||
btrfs_releasepage(page, GFP_NOFS);
|
||||
return;
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue