syzbot


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

Status: auto-closed as invalid on 2021/11/25 03:42
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 432d, last: 411d
similar bugs (9):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in __mark_inode_dirty / writeback_sb_inodes (5) 1 358d 358d 0/24 auto-closed as invalid on 2022/01/16 16:04
upstream KCSAN: data-race in __mark_inode_dirty / writeback_sb_inodes 38 911d 1132d 0/24 closed as invalid on 2020/06/18 14:24
upstream KCSAN: data-race in __mark_inode_dirty / writeback_sb_inodes (3) 2 472d 474d 0/24 auto-closed as invalid on 2021/09/25 11:37
upstream KCSAN: data-race in __mark_inode_dirty / writeback_sb_inodes (7) 2 200d 232d 0/24 auto-closed as invalid on 2022/06/23 15:49
upstream KCSAN: data-race in __mark_inode_dirty / writeback_sb_inodes (2) 70 538d 764d 0/24 auto-closed as invalid on 2021/07/20 20:13
upstream KCSAN: data-race in __mark_inode_dirty / writeback_sb_inodes (8) 2 156d 164d 0/24 auto-closed as invalid on 2022/08/07 13:58
upstream KCSAN: data-race in __mark_inode_dirty / writeback_sb_inodes (10) 1 58d 58d 0/24 auto-obsoleted due to no activity on 2022/11/12 17:32
upstream KCSAN: data-race in __mark_inode_dirty / writeback_sb_inodes (9) 1 117d 117d 0/24 auto-closed as invalid on 2022/09/14 22:08
upstream KCSAN: data-race in __mark_inode_dirty / writeback_sb_inodes (6) 1 288d 288d 0/24 auto-closed as invalid on 2022/03/28 07:47

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

write to 0xffff888104a257e0 of 8 bytes by task 8 on cpu 1:
 writeback_sb_inodes+0x9e9/0xd30 fs/fs-writeback.c:1908
 wb_writeback+0x27d/0x6d0 fs/fs-writeback.c:2053
 wb_do_writeback+0x101/0x530 fs/fs-writeback.c:2196
 wb_workfn+0xc8/0x540 fs/fs-writeback.c:2237
 process_one_work+0x402/0x910 kernel/workqueue.c:2297
 worker_thread+0x636/0xae0 kernel/workqueue.c:2444
 kthread+0x262/0x280 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30

read to 0xffff888104a257e0 of 8 bytes by task 7077 on cpu 0:
 __mark_inode_dirty+0xda/0x6a0 fs/fs-writeback.c:2419
 mark_inode_dirty include/linux/fs.h:2452 [inline]
 generic_write_end+0x157/0x180 fs/buffer.c:2202
 ext4_da_write_end+0x4cc/0x5e0 fs/ext4/inode.c:3062
 generic_perform_write+0x251/0x3e0 mm/filemap.c:3781
 ext4_buffered_write_iter+0x305/0x400 fs/ext4/file.c:269
 ext4_file_write_iter+0x2e7/0x11f0
 call_write_iter include/linux/fs.h:2163 [inline]
 aio_write+0x2b4/0x390 fs/aio.c:1578
 io_submit_one+0x86f/0x13b0 fs/aio.c:1880
 __do_sys_io_submit fs/aio.c:1939 [inline]
 __se_sys_io_submit+0x105/0x270 fs/aio.c:1909
 __x64_sys_io_submit+0x3f/0x50 fs/aio.c:1909
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x44/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x0000000000020084 -> 0x0000000000000004

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 7077 Comm: syz-executor.5 Not tainted 5.15.0-rc6-syzkaller #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 2021/10/21 03:41 upstream 2f111a6fd5b5 f111d03b .config log report info KCSAN: data-race in __mark_inode_dirty / writeback_sb_inodes
ci2-upstream-kcsan-gce 2021/09/29 19:25 upstream a4e6f95a891a e08fe937 .config log report info KCSAN: data-race in __mark_inode_dirty / writeback_sb_inodes
* Struck through repros no longer work on HEAD.