Ye Bin
1da18e38cb
ext4: fix reserved cluster accounting in __es_remove_extent()
...
When bigalloc is enabled, reserved cluster accounting for delayed
allocation is handled in extent_status.c. With a corrupted file
system, it's possible for this accounting to be incorrect,
dsicovered by Syzbot:
EXT4-fs error (device loop0): ext4_validate_block_bitmap:398: comm rep:
bg 0: block 5: invalid block bitmap
EXT4-fs (loop0): Delayed block allocation failed for inode 18 at logical
offset 0 with max blocks 32 with error 28
EXT4-fs (loop0): This should not happen!! Data will be lost
EXT4-fs (loop0): Total free blocks count 0
EXT4-fs (loop0): Free/Dirty block details
EXT4-fs (loop0): free_blocks=0
EXT4-fs (loop0): dirty_blocks=32
EXT4-fs (loop0): Block reservation details
EXT4-fs (loop0): i_reserved_data_blocks=2
EXT4-fs (loop0): Inode 18 (00000000845cd634):
i_reserved_data_blocks (1) not cleared!
Above issue happens as follows:
Assume:
sbi->s_cluster_ratio = 16
Step1:
Insert delay block [0, 31] -> ei->i_reserved_data_blocks=2
Step2:
ext4_writepages
mpage_map_and_submit_extent -> return failed
mpage_release_unused_pages -> to release [0, 30]
ext4_es_remove_extent -> remove lblk=0 end=30
__es_remove_extent -> len1=0 len2=31-30=1
__es_remove_extent:
...
if (len2 > 0) {
...
if (len1 > 0) {
...
} else {
es->es_lblk = end + 1;
es->es_len = len2;
...
}
if (count_reserved)
count_rsvd(inode, lblk, ...);
goto out; -> will return but didn't calculate 'reserved'
...
Step3:
ext4_destroy_inode -> trigger "i_reserved_data_blocks (1) not cleared!"
To solve above issue if 'len2>0' call 'get_rsvd()' before goto out.
Reported-by: syzbot+05a0f0ccab4a25626e38@syzkaller.appspotmail.com
Fixes: 8fcc3a580651 ("ext4: rework reserved cluster accounting when invalidating pages")
Signed-off-by: Ye Bin <yebin10@huawei.com>
Reviewed-by: Eric Whitney <enwlinux@gmail.com>
Link: https://lore.kernel.org/r/20221208033426.1832460-2-yebin@huaweicloud.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@kernel.org
2022-12-09 00:58:04 -05:00
..
2021-02-11 23:16:30 -05:00
2022-02-03 10:57:53 -05:00
2021-08-18 22:08:24 +02:00
2022-08-02 23:52:19 -04:00
2017-11-02 11:10:55 +01:00
2022-02-25 21:34:56 -05:00
2022-05-21 22:24:24 -04:00
2022-05-11 15:19:06 -04:00
2021-08-30 23:36:50 -04:00
2022-12-01 10:46:54 -05:00
2022-12-01 10:46:54 -05:00
2022-12-08 21:49:25 -05:00
2022-12-09 00:58:04 -05:00
2020-01-25 02:03:03 -05:00
2022-12-08 21:49:25 -05:00
2022-12-08 21:49:25 -05:00
2022-12-08 21:49:24 -05:00
2022-10-06 17:45:53 -07:00
2021-04-08 16:04:22 -07:00
2021-06-24 09:48:29 -04:00
2021-01-27 09:51:48 -07:00
2022-01-20 19:57:24 -05:00
2022-12-01 10:46:54 -05:00
2022-12-08 21:49:24 -05:00
2022-11-29 16:10:49 -05:00
2020-12-02 16:07:25 -07:00
2022-12-08 22:03:15 -05:00
2022-12-08 22:03:15 -05:00
2021-02-11 23:12:59 -05:00
2022-05-21 22:24:24 -04:00
2022-12-08 21:49:25 -05:00
2022-09-21 22:12:03 -04:00
2022-11-06 01:07:59 -04:00
2022-10-11 17:42:58 -06:00
2022-09-30 23:46:54 -04:00
2022-12-08 21:49:24 -05:00
2022-12-08 21:49:23 -05:00
2022-12-08 21:49:25 -05:00
2022-12-08 21:49:24 -05:00
2022-12-08 21:49:24 -05:00
2022-12-08 21:49:25 -05:00
2022-08-02 23:37:50 -04:00
2022-01-20 19:57:24 -05:00
2021-07-13 14:29:00 +02:00
2022-12-08 21:49:25 -05:00
2021-01-24 14:27:17 +01:00
2021-01-24 14:27:17 +01:00
2021-01-24 14:27:17 +01:00
2021-01-24 14:27:17 +01:00
2022-12-09 00:57:01 -05:00
2022-08-02 23:56:25 -04:00