syzbot


KCSAN: data-race in __mark_inode_dirty / inode_cgwb_move_to_attached (8)

Status: moderation: reported on 2025/03/15 05:56
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+838e56e1d279904a0763@syzkaller.appspotmail.com
First crash: 4h53m, last: 4h53m
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in __mark_inode_dirty / inode_cgwb_move_to_attached (3) exfat 1 1206d 1206d 0/28 auto-closed as invalid on 2021/12/29 19:13
upstream KCSAN: data-race in __mark_inode_dirty / inode_cgwb_move_to_attached (6) ext4 1 174d 174d 0/28 auto-obsoleted due to no activity on 2024/10/27 07:39
upstream KCSAN: data-race in __mark_inode_dirty / inode_cgwb_move_to_attached (2) ext4 1 1256d 1256d 0/28 auto-closed as invalid on 2021/11/09 15:48
upstream KCSAN: data-race in __mark_inode_dirty / inode_cgwb_move_to_attached (5) ext4 1 713d 713d 0/28 auto-obsoleted due to no activity on 2023/05/07 10:14
upstream KCSAN: data-race in __mark_inode_dirty / inode_cgwb_move_to_attached (4) ext4 1 1026d 1026d 0/28 auto-closed as invalid on 2022/06/28 09:48
upstream KCSAN: data-race in __mark_inode_dirty / inode_cgwb_move_to_attached (7) ext4 1 119d 119d 0/28 auto-obsoleted due to no activity on 2025/01/10 12:23
upstream KCSAN: data-race in __mark_inode_dirty / inode_cgwb_move_to_attached ext4 1 1292d 1292d 0/28 auto-closed as invalid on 2021/10/05 03:36

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

write to 0xffff8881065d8f38 of 4 bytes by task 3700 on cpu 1:
 inode_cgwb_move_to_attached+0x9a/0x300 fs/fs-writeback.c:309
 writeback_sb_inodes+0x6a6/0xa30 fs/fs-writeback.c:2005
 wb_writeback+0x262/0x640 fs/fs-writeback.c:2156
 wb_do_writeback fs/fs-writeback.c:2303 [inline]
 wb_workfn+0x1a8/0x940 fs/fs-writeback.c:2343
 process_one_work kernel/workqueue.c:3238 [inline]
 process_scheduled_works+0x4db/0xa20 kernel/workqueue.c:3319
 worker_thread+0x51d/0x6f0 kernel/workqueue.c:3400
 kthread+0x4ae/0x520 kernel/kthread.c:464
 ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

read to 0xffff8881065d8f38 of 4 bytes by task 25299 on cpu 0:
 __mark_inode_dirty+0x58/0x7e0 fs/fs-writeback.c:2497
 generic_update_time fs/inode.c:2112 [inline]
 inode_update_time fs/inode.c:2125 [inline]
 __file_update_time fs/inode.c:2353 [inline]
 file_update_time+0x285/0x2b0 fs/inode.c:2383
 ext4_page_mkwrite+0x19e/0xb70 fs/ext4/inode.c:6160
 do_page_mkwrite mm/memory.c:3257 [inline]
 wp_page_shared mm/memory.c:3658 [inline]
 do_wp_page+0xca1/0x2340 mm/memory.c:3808
 handle_pte_fault mm/memory.c:5923 [inline]
 __handle_mm_fault mm/memory.c:6050 [inline]
 handle_mm_fault+0xc63/0x2ac0 mm/memory.c:6219
 do_user_addr_fault arch/x86/mm/fault.c:1337 [inline]
 handle_page_fault arch/x86/mm/fault.c:1480 [inline]
 exc_page_fault+0x3b9/0x650 arch/x86/mm/fault.c:1538
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623

value changed: 0x00010002 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 25299 Comm: syz.4.6605 Not tainted 6.14.0-rc6-syzkaller-00202-ga29967be967e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/15 05:55 upstream a29967be967e e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in __mark_inode_dirty / inode_cgwb_move_to_attached
* Struck through repros no longer work on HEAD.