syzbot


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

Status: auto-obsoleted due to no activity on 2023/05/07 10:14
Subsystems: ext4
[Documentation on labels]
First crash: 394d, last: 394d
Similar bugs (4)
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 888d 888d 0/26 auto-closed as invalid on 2021/12/29 19:13
upstream KCSAN: data-race in __mark_inode_dirty / inode_cgwb_move_to_attached (2) ext4 1 938d 938d 0/26 auto-closed as invalid on 2021/11/09 15:48
upstream KCSAN: data-race in __mark_inode_dirty / inode_cgwb_move_to_attached (4) ext4 1 707d 707d 0/26 auto-closed as invalid on 2022/06/28 09:48
upstream KCSAN: data-race in __mark_inode_dirty / inode_cgwb_move_to_attached ext4 1 973d 973d 0/26 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 0xffff88810a4c63c0 of 8 bytes by task 27880 on cpu 0:
 inode_cgwb_move_to_attached+0x9c/0x2f0 fs/fs-writeback.c:286
 requeue_inode fs/fs-writeback.c:1573 [inline]
 writeback_sb_inodes+0x7ec/0xaa0 fs/fs-writeback.c:1920
 wb_writeback+0x23b/0x6c0 fs/fs-writeback.c:2065
 wb_do_writeback fs/fs-writeback.c:2208 [inline]
 wb_workfn+0x1a8/0x8d0 fs/fs-writeback.c:2248
 process_one_work+0x3e6/0x750 kernel/workqueue.c:2390
 worker_thread+0x5f2/0xa10 kernel/workqueue.c:2537
 kthread+0x1ac/0x1e0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308

read to 0xffff88810a4c63c0 of 8 bytes by task 22906 on cpu 1:
 __mark_inode_dirty+0x58/0x7d0 fs/fs-writeback.c:2403
 mark_inode_dirty_sync include/linux/fs.h:2132 [inline]
 dquot_free_space include/linux/quotaops.h:385 [inline]
 dquot_free_block include/linux/quotaops.h:395 [inline]
 ext4_mb_new_blocks+0x1776/0x21c0 fs/ext4/mballoc.c:5654
 ext4_ext_map_blocks+0xe1f/0x36c0 fs/ext4/extents.c:4286
 ext4_map_blocks+0x738/0x1050 fs/ext4/inode.c:651
 ext4_alloc_file_blocks+0x272/0x6d0 fs/ext4/extents.c:4470
 ext4_zero_range+0x32b/0x890 fs/ext4/extents.c:4587
 ext4_fallocate+0x3a3/0x12b0 fs/ext4/extents.c:4722
 vfs_fallocate+0x369/0x3d0 fs/open.c:324
 ksys_fallocate fs/open.c:347 [inline]
 __do_sys_fallocate fs/open.c:355 [inline]
 __se_sys_fallocate fs/open.c:353 [inline]
 __x64_sys_fallocate+0x79/0xc0 fs/open.c:353
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

value changed: 0x0000000000020080 -> 0x0000000000000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 22906 Comm: syz-executor.2 Not tainted 6.3.0-rc4-syzkaller-00224-g00c7b5f4ddc5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/04/02 10:14 upstream 00c7b5f4ddc5 f325deb0 .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.