syzbot


KCSAN: data-race in __ext4_handle_dirty_metadata / jbd2_journal_update_sb_log_tail (3)

Status: closed as invalid on 2022/05/13 11:20
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 203d, last: 201d
similar bugs (2):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in __ext4_handle_dirty_metadata / jbd2_journal_update_sb_log_tail (2) 6 350d 406d 0/24 auto-closed as invalid on 2022/01/16 21:04
upstream KCSAN: data-race in __ext4_handle_dirty_metadata / jbd2_journal_update_sb_log_tail 1 659d 659d 0/24 auto-closed as invalid on 2021/03/13 20:27

Sample crash report:
==================================================================
BUG: KCSAN: data-race in __ext4_handle_dirty_metadata / jbd2_journal_update_sb_log_tail

read-write to 0xffff888103e0e000 of 8 bytes by task 1405 on cpu 1:
 jbd2_journal_update_sb_log_tail+0x16e/0x1a0 fs/jbd2/journal.c:1695
 jbd2_journal_commit_transaction+0x22a/0x3180 fs/jbd2/commit.c:430
 kjournald2+0x253/0x460 fs/jbd2/journal.c:213
 kthread+0x1a9/0x1e0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30

read to 0xffff888103e0e000 of 8 bytes by task 1839 on cpu 0:
 is_journal_aborted include/linux/jbd2.h:1689 [inline]
 is_handle_aborted include/linux/jbd2.h:1696 [inline]
 __ext4_handle_dirty_metadata+0x138/0x470 fs/ext4/ext4_jbd2.c:352
 ext4_do_update_inode fs/ext4/inode.c:5143 [inline]
 ext4_mark_iloc_dirty+0x512/0x860 fs/ext4/inode.c:5724
 __ext4_mark_inode_dirty+0x452/0x610 fs/ext4/inode.c:5920
 ext4_dirty_inode+0x86/0xa0 fs/ext4/inode.c:5949
 __mark_inode_dirty+0x70/0x5f0 fs/fs-writeback.c:2367
 mark_inode_dirty include/linux/fs.h:2324 [inline]
 dquot_alloc_space include/linux/quotaops.h:317 [inline]
 dquot_alloc_block include/linux/quotaops.h:334 [inline]
 ext4_mb_new_blocks+0xce3/0xfd0 fs/ext4/mballoc.c:5578
 ext4_ext_map_blocks+0xd55/0x1bb0 fs/ext4/extents.c:4281
 ext4_map_blocks+0x75b/0xfc0 fs/ext4/inode.c:636
 ext4_getblk+0xcb/0x410 fs/ext4/inode.c:847
 ext4_bread+0x28/0x100 fs/ext4/inode.c:900
 ext4_append+0xd1/0x1c0 fs/ext4/namei.c:67
 ext4_init_new_dir+0x177/0x500 fs/ext4/namei.c:2893
 ext4_mkdir+0x329/0x760 fs/ext4/namei.c:2939
 vfs_mkdir+0x216/0x320 fs/namei.c:3931
 do_mkdirat+0x105/0x280 fs/namei.c:3957
 __do_sys_mkdirat fs/namei.c:3972 [inline]
 __se_sys_mkdirat fs/namei.c:3970 [inline]
 __x64_sys_mkdirat+0x4c/0x60 fs/namei.c:3970
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x0000000000000038 -> 0x0000000000000230

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 1839 Comm: syz-executor.4 Not tainted 5.18.0-rc6-syzkaller-00009-gfeb9c5e19e91 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================

Crashes (2):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-upstream-kcsan-gce 2022/05/11 05:24 upstream feb9c5e19e91 8d7b3b67 .config log report info KCSAN: data-race in __ext4_handle_dirty_metadata / jbd2_journal_update_sb_log_tail
ci2-upstream-kcsan-gce 2022/05/08 21:51 upstream 379c72654524 e60b1103 .config log report info KCSAN: data-race in __ext4_handle_dirty_metadata / jbd2_journal_update_sb_log_tail
* Struck through repros no longer work on HEAD.