syzbot


KCSAN: data-race in __mark_inode_dirty / redirty_tail_locked (4)

Status: auto-obsoleted due to no activity on 2024/01/09 20:12
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+617d96451460fe1860f7@syzkaller.appspotmail.com
First crash: 176d, last: 176d
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in __mark_inode_dirty / redirty_tail_locked (2) ext4 10 278d 413d 0/26 auto-obsoleted due to no activity on 2023/09/29 00:10
upstream KCSAN: data-race in __mark_inode_dirty / redirty_tail_locked (5) ext4 1 120d 120d 0/26 auto-obsoleted due to no activity on 2024/03/05 08:43
upstream KCSAN: data-race in __mark_inode_dirty / redirty_tail_locked (3) ext4 3 214d 239d 0/26 auto-obsoleted due to no activity on 2023/12/02 13:09
upstream KCSAN: data-race in __mark_inode_dirty / redirty_tail_locked (6) ext4 1 60d 60d 0/26 auto-obsoleted due to no activity on 2024/05/04 07:48
upstream KCSAN: data-race in __mark_inode_dirty / redirty_tail_locked ext4 1 481d 481d 0/26 auto-obsoleted due to no activity on 2023/03/31 02:53

Sample crash report:
==================================================================
BUG: KCSAN: data-race in __mark_inode_dirty / redirty_tail_locked

read-write to 0xffff888107da6ad0 of 8 bytes by task 14521 on cpu 1:
 redirty_tail_locked+0x56/0x270 fs/fs-writeback.c:1322
 requeue_inode fs/fs-writeback.c:1583 [inline]
 writeback_sb_inodes+0x7dd/0xad0 fs/fs-writeback.c:1945
 wb_writeback+0x252/0x6e0 fs/fs-writeback.c:2092
 wb_do_writeback fs/fs-writeback.c:2239 [inline]
 wb_workfn+0x1a8/0x8d0 fs/fs-writeback.c:2279
 process_one_work kernel/workqueue.c:2630 [inline]
 process_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703
 worker_thread+0x525/0x730 kernel/workqueue.c:2784
 kthread+0x1d7/0x210 kernel/kthread.c:388
 ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

read to 0xffff888107da6ad0 of 8 bytes by task 22963 on cpu 0:
 __mark_inode_dirty+0x199/0x7d0 fs/fs-writeback.c:2474
 mark_buffer_dirty+0x165/0x240 fs/buffer.c:1204
 __block_commit_write fs/buffer.c:2191 [inline]
 block_write_end+0x158/0x2e0 fs/buffer.c:2267
 ext4_da_do_write_end fs/ext4/inode.c:2961 [inline]
 ext4_da_write_end+0x1fc/0x9c0 fs/ext4/inode.c:3033
 generic_perform_write+0x267/0x410 mm/filemap.c:3929
 ext4_buffered_write_iter+0x1f6/0x370 fs/ext4/file.c:299
 ext4_file_write_iter+0x297/0xe10
 call_write_iter include/linux/fs.h:2020 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x48a/0x790 fs/read_write.c:584
 ksys_write+0xeb/0x1a0 fs/read_write.c:637
 __do_sys_write fs/read_write.c:649 [inline]
 __se_sys_write fs/read_write.c:646 [inline]
 __x64_sys_write+0x42/0x50 fs/read_write.c:646
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
 entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x0000000000020084 -> 0x0000000000000004

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 22963 Comm: syz-executor.1 Not tainted 6.7.0-rc4-syzkaller-00009-gbee0e7762ad2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/12/05 20:12 upstream bee0e7762ad2 858d62d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in __mark_inode_dirty / redirty_tail_locked
* Struck through repros no longer work on HEAD.