syzbot


KCSAN: data-race in jbd2_journal_commit_transaction / jbd2_log_wait_commit (3)

Status: auto-closed as invalid on 2022/03/10 19:58
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 309d, last: 307d
similar bugs (3):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in jbd2_journal_commit_transaction / jbd2_log_wait_commit (4) 4 210d 211d 0/24 closed as invalid on 2022/05/13 11:20
upstream KCSAN: data-race in jbd2_journal_commit_transaction / jbd2_log_wait_commit 2 640d 640d 0/24 auto-closed as invalid on 2021/04/11 22:19
upstream KCSAN: data-race in jbd2_journal_commit_transaction / jbd2_log_wait_commit (2) 76 351d 375d 0/24 auto-closed as invalid on 2022/01/25 10:22

Sample crash report:
==================================================================
BUG: KCSAN: data-race in jbd2_journal_commit_transaction / jbd2_log_wait_commit

write to 0xffff888103d45468 of 4 bytes by task 1404 on cpu 1:
 jbd2_journal_commit_transaction+0x2a77/0x3460 fs/jbd2/commit.c:1154
 kjournald2+0x263/0x480 fs/jbd2/journal.c:213
 kthread+0x1bf/0x1e0 kernel/kthread.c:377
 ret_from_fork+0x1f/0x30

read to 0xffff888103d45468 of 4 bytes by task 24797 on cpu 0:
 jbd2_log_wait_commit+0xb3/0x210 fs/jbd2/journal.c:712
 jbd2_complete_transaction+0xfb/0x110 fs/jbd2/journal.c:848
 ext4_fc_commit+0xd9/0x14e0
 ext4_fsync_journal fs/ext4/fsync.c:115 [inline]
 ext4_sync_file+0x336/0x6e0 fs/ext4/fsync.c:174
 vfs_fsync_range+0x107/0x120 fs/sync.c:182
 generic_write_sync include/linux/fs.h:2884 [inline]
 ext4_buffered_write_iter+0x318/0x360 fs/ext4/file.c:275
 ext4_file_write_iter+0x2e7/0x11f0
 call_write_iter include/linux/fs.h:2074 [inline]
 do_iter_readv_writev+0x2de/0x380 fs/read_write.c:725
 do_iter_write+0x192/0x5c0 fs/read_write.c:851
 vfs_iter_write+0x4c/0x70 fs/read_write.c:892
 iter_file_splice_write+0x43a/0x790 fs/splice.c:689
 do_splice_from fs/splice.c:767 [inline]
 direct_splice_actor+0x80/0xa0 fs/splice.c:936
 splice_direct_to_actor+0x345/0x650 fs/splice.c:891
 do_splice_direct+0x106/0x190 fs/splice.c:979
 do_sendfile+0x675/0xc40 fs/read_write.c:1245
 __do_sys_sendfile64 fs/read_write.c:1304 [inline]
 __se_sys_sendfile64 fs/read_write.c:1296 [inline]
 __x64_sys_sendfile64+0xb9/0x140 fs/read_write.c:1296
 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: 0x00000bb9 -> 0x00000bba

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 24797 Comm: syz-executor.1 Tainted: G        W         5.17.0-rc2-syzkaller-00064-gc36c04c2e132 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================

Crashes (4):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-upstream-kcsan-gce 2022/02/03 19:50 upstream c36c04c2e132 30646bfe .config log report info KCSAN: data-race in jbd2_journal_commit_transaction / jbd2_log_wait_commit
ci2-upstream-kcsan-gce 2022/02/03 16:24 upstream 88808fbbead4 4ebb2798 .config log report info KCSAN: data-race in jbd2_journal_commit_transaction / jbd2_log_wait_commit
ci2-upstream-kcsan-gce 2022/02/02 22:31 upstream 27bb0b18c208 4ebb2798 .config log report info KCSAN: data-race in jbd2_journal_commit_transaction / jbd2_log_wait_commit
ci2-upstream-kcsan-gce 2022/02/01 22:53 upstream 9f7fb8de5d9b 4ebb2798 .config log report info KCSAN: data-race in jbd2_journal_commit_transaction / jbd2_log_wait_commit
* Struck through repros no longer work on HEAD.