Baokun Li
18881d7e51
ext4: fix race condition between ext4_write and ext4_convert_inline_data
...
commit f87c7a4b084afc13190cbb263538e444cb2b392a upstream.
Hulk Robot reported a BUG_ON:
==================================================================
EXT4-fs error (device loop3): ext4_mb_generate_buddy:805: group 0,
block bitmap and bg descriptor inconsistent: 25 vs 31513 free clusters
kernel BUG at fs/ext4/ext4_jbd2.c:53!
invalid opcode: 0000 [#1 ] SMP KASAN PTI
CPU: 0 PID: 25371 Comm: syz-executor.3 Not tainted 5.10.0+ #1
RIP: 0010:ext4_put_nojournal fs/ext4/ext4_jbd2.c:53 [inline]
RIP: 0010:__ext4_journal_stop+0x10e/0x110 fs/ext4/ext4_jbd2.c:116
[...]
Call Trace:
ext4_write_inline_data_end+0x59a/0x730 fs/ext4/inline.c:795
generic_perform_write+0x279/0x3c0 mm/filemap.c:3344
ext4_buffered_write_iter+0x2e3/0x3d0 fs/ext4/file.c:270
ext4_file_write_iter+0x30a/0x11c0 fs/ext4/file.c:520
do_iter_readv_writev+0x339/0x3c0 fs/read_write.c:732
do_iter_write+0x107/0x430 fs/read_write.c:861
vfs_writev fs/read_write.c:934 [inline]
do_pwritev+0x1e5/0x380 fs/read_write.c:1031
[...]
==================================================================
Above issue may happen as follows:
cpu1 cpu2
__________________________|__________________________
do_pwritev
vfs_writev
do_iter_write
ext4_file_write_iter
ext4_buffered_write_iter
generic_perform_write
ext4_da_write_begin
vfs_fallocate
ext4_fallocate
ext4_convert_inline_data
ext4_convert_inline_data_nolock
ext4_destroy_inline_data_nolock
clear EXT4_STATE_MAY_INLINE_DATA
ext4_map_blocks
ext4_ext_map_blocks
ext4_mb_new_blocks
ext4_mb_regular_allocator
ext4_mb_good_group_nolock
ext4_mb_init_group
ext4_mb_init_cache
ext4_mb_generate_buddy --> error
ext4_test_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA)
ext4_restore_inline_data
set EXT4_STATE_MAY_INLINE_DATA
ext4_block_write_begin
ext4_da_write_end
ext4_test_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA)
ext4_write_inline_data_end
handle=NULL
ext4_journal_stop(handle)
__ext4_journal_stop
ext4_put_nojournal(handle)
ref_cnt = (unsigned long)handle
BUG_ON(ref_cnt == 0) ---> BUG_ON
The lock held by ext4_convert_inline_data is xattr_sem, but the lock
held by generic_perform_write is i_rwsem. Therefore, the two locks can
be concurrent.
To solve above issue, we add inode_lock() for ext4_convert_inline_data().
At the same time, move ext4_convert_inline_data() in front of
ext4_punch_hole(), remove similar handling from ext4_punch_hole().
Fixes: 0c8d414f163f ("ext4: let fallocate handle inline data correctly")
Cc: stable@vger.kernel.org
Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: Baokun Li <libaokun1@huawei.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Link: https://lore.kernel.org/r/20220428134031.4153381-1-libaokun1@huawei.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Tadeusz Struk <tadeusz.struk@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2022-07-21 20:59:18 +02:00
..
2022-06-22 14:11:02 +02:00
2021-03-04 10:26:48 +01:00
2022-06-29 08:58:46 +02:00
2019-10-25 00:03:11 -04:00
2021-01-06 14:48:39 +01:00
2022-06-14 18:11:24 +02:00
2020-11-05 11:43:36 +01:00
2022-06-14 18:12:01 +02:00
2022-06-14 18:12:02 +02:00
2019-09-19 09:42:37 -07:00
2022-03-02 11:41:10 +01:00
2019-11-23 21:44:49 -05:00
2021-09-12 08:56:38 +02:00
2022-01-27 09:19:36 +01:00
2022-02-01 17:24:34 +01:00
2022-06-14 18:11:46 +02:00
2021-05-26 12:05:19 +02:00
2020-12-02 08:49:53 +01:00
2021-11-21 13:38:51 +01:00
2019-11-10 11:56:05 -05:00
2022-04-15 14:18:13 +02:00
2022-07-21 20:59:18 +02:00
2022-06-14 18:11:56 +02:00
2022-06-14 18:11:30 +02:00
2021-09-22 12:26:25 +02:00
2022-03-16 13:21:47 +01:00
2022-05-18 09:47:26 +02:00
2021-07-31 08:19:38 +02:00
2021-05-19 10:08:29 +02:00
2021-04-14 08:24:14 +02:00
2022-05-09 09:03:28 +02:00
2022-06-14 18:11:36 +02:00
2021-11-12 14:43:03 +01:00
2022-04-27 13:50:50 +02:00
2022-06-14 18:11:55 +02:00
2022-06-14 18:11:29 +02:00
2022-06-14 18:12:00 +02:00
2021-09-22 12:26:34 +02:00
2022-04-15 14:18:35 +02:00
2022-06-22 14:11:21 +02:00
2020-12-30 11:51:22 +01:00
2022-06-06 08:33:51 +02:00
2022-07-21 20:59:18 +02:00
2022-06-14 18:11:34 +02:00
2022-04-15 14:18:23 +02:00
2022-06-14 18:11:46 +02:00
2022-01-20 09:19:17 +01:00
2021-12-22 09:29:40 +01:00
2022-06-14 18:11:41 +02:00
2021-03-04 10:26:45 +01:00
2021-09-30 10:09:26 +02:00
2022-02-23 11:59:55 +01:00
2020-10-29 09:57:53 +01:00
2021-08-12 13:21:05 +02:00
2020-08-26 10:40:51 +02:00
2021-05-19 10:08:29 +02:00
2021-03-07 12:20:48 +01:00
2022-03-02 11:41:13 +01:00
2022-04-15 14:18:31 +02:00
2022-02-01 17:24:34 +01:00
2020-08-21 13:05:37 +02:00
2019-09-17 11:48:24 -04:00
2021-10-06 15:42:30 +02:00
2022-07-12 16:30:48 +02:00
2021-12-14 14:49:02 +01:00
2020-02-11 04:35:12 -08:00
2021-10-06 15:42:35 +02:00
2022-06-14 18:11:23 +02:00
2021-03-17 17:03:57 +01:00
2021-05-22 11:38:29 +02:00
2020-11-05 11:43:24 +01:00
2020-01-14 20:08:18 +01:00
2022-06-22 14:11:03 +02:00
2020-12-11 13:23:30 +01:00
2020-10-29 09:57:45 +01:00
2022-06-14 18:11:41 +02:00
2020-10-01 13:17:19 +02:00
2021-04-14 08:24:11 +02:00
2020-01-12 12:21:37 +01:00
2020-02-11 04:35:37 -08:00
2020-10-07 08:01:31 +02:00
2022-06-06 08:33:50 +02:00
2021-09-15 09:47:28 +02:00
2022-05-25 09:14:34 +02:00
2022-03-02 11:41:18 +01:00
2020-04-17 10:50:21 +02:00
2022-02-08 18:24:29 +01:00
2019-09-12 21:06:14 -04:00
2022-06-14 18:11:44 +02:00
2020-03-25 08:25:58 +01:00
2021-07-31 08:19:37 +02:00
2022-04-15 14:18:41 +02:00
2019-12-17 19:55:30 +01:00
2019-09-18 16:59:14 -07:00
2020-11-24 13:29:19 +01:00
2020-03-25 08:25:41 +01:00
2019-09-18 16:59:14 -07:00
2020-01-17 19:48:21 +01:00
2022-02-01 17:24:39 +01:00
2021-08-26 08:36:22 -04:00
2020-03-18 07:17:51 +01:00
2021-08-12 13:21:02 +02:00
2020-05-02 08:48:44 +02:00
2021-03-17 17:03:33 +01:00
2020-02-11 04:35:23 -08:00
2021-04-21 12:56:16 +02:00
2022-01-29 10:25:11 +01:00
2021-07-20 16:10:54 +02:00
2021-12-14 14:49:02 +01:00
2019-12-17 19:56:52 +01:00
2022-04-27 13:50:48 +02:00
2019-10-03 14:21:35 -07:00
2022-02-23 11:59:55 +01:00
2021-09-22 12:26:26 +02:00
2020-02-11 04:35:12 -08:00
2020-08-11 15:33:39 +02:00