syzbot


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

Status: auto-closed as invalid on 2022/01/16 21:04
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 473d, last: 417d
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 1 726d 726d 0/24 auto-closed as invalid on 2021/03/13 20:27
upstream KCSAN: data-race in __ext4_handle_dirty_metadata / jbd2_journal_update_sb_log_tail (3) 2 268d 270d 0/24 closed as invalid on 2022/05/13 11:20

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

write to 0xffff888102fd3000 of 8 bytes by task 1402 on cpu 1:
 jbd2_journal_update_sb_log_tail+0x176/0x1b0 fs/jbd2/journal.c:1689
 jbd2_journal_commit_transaction+0x21e/0x3460 fs/jbd2/commit.c:430
 kjournald2+0x263/0x480 fs/jbd2/journal.c:213
 kthread+0x2c7/0x2e0 kernel/kthread.c:327
 ret_from_fork+0x1f/0x30

read to 0xffff888102fd3000 of 8 bytes by task 22704 on cpu 0:
 is_journal_aborted include/linux/jbd2.h:1695 [inline]
 is_handle_aborted include/linux/jbd2.h:1702 [inline]
 __ext4_handle_dirty_metadata+0x14f/0x5a0 fs/ext4/ext4_jbd2.c:350
 ext4_do_update_inode fs/ext4/inode.c:5106 [inline]
 ext4_mark_iloc_dirty+0x513/0x890 fs/ext4/inode.c:5694
 ext4_xattr_set_handle+0xf77/0x1120 fs/ext4/xattr.c:2402
 ext4_initxattrs+0x66/0xb0 fs/ext4/xattr_security.c:44
 security_inode_init_security+0x1a9/0x260 security/security.c:1100
 ext4_init_security+0x30/0x40 fs/ext4/xattr_security.c:58
 __ext4_new_inode+0x29a3/0x2fc0 fs/ext4/ialloc.c:1325
 ext4_symlink+0x2cc/0x700 fs/ext4/namei.c:3293
 vfs_symlink+0x241/0x330 fs/namei.c:4248
 do_symlinkat+0x104/0x380 fs/namei.c:4277
 __do_sys_symlink fs/namei.c:4299 [inline]
 __se_sys_symlink fs/namei.c:4297 [inline]
 __x64_sys_symlink+0x52/0x60 fs/namei.c:4297
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x44/0xd0 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: 22704 Comm: syz-executor.3 Not tainted 5.16.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================

Crashes (6):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci2-upstream-kcsan-gce 2021/12/12 20:56 upstream 90d9fbc16b69 49ca1f59 .config console log report info KCSAN: data-race in __ext4_handle_dirty_metadata / jbd2_journal_update_sb_log_tail
ci2-upstream-kcsan-gce 2021/11/23 06:22 upstream 136057256686 545ab074 .config console log report info KCSAN: data-race in __ext4_handle_dirty_metadata / jbd2_journal_update_sb_log_tail
ci2-upstream-kcsan-gce 2021/11/14 17:44 upstream c8c109546a19 75b04091 .config console log report info KCSAN: data-race in __ext4_handle_dirty_metadata / jbd2_journal_update_sb_log_tail
ci2-upstream-kcsan-gce 2021/10/27 01:58 upstream 3906fe9bb7f1 d50eb50a .config console log report info KCSAN: data-race in __ext4_handle_dirty_metadata / jbd2_journal_update_sb_log_tail
ci2-upstream-kcsan-gce 2021/10/25 23:46 upstream 87066fdd2e30 c1132b49 .config console log report info KCSAN: data-race in __ext4_handle_dirty_metadata / jbd2_journal_update_sb_log_tail
ci2-upstream-kcsan-gce 2021/10/18 07:25 upstream cf52ad5ff16c 0c5d9412 .config console 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.