Hello, syzbot found the following issue on: HEAD commit: 6537cfb395f3 Merge tag 'sound-6.14-rc4' of git://git.kerne.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10291498580000 kernel config: https://syzkaller.appspot.com/x/.config?x=ce4e433ac2a58cc2 dashboard link: https://syzkaller.appspot.com/bug?extid=6c0e241874a0c6a56ec2 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/a486bd4f9ce1/disk-6537cfb3.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/6b6efb477de2/vmlinux-6537cfb3.xz kernel image: https://storage.googleapis.com/syzbot-assets/3a4c3dd86651/bzImage-6537cfb3.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+6c0e241874a0c6a56ec2@xxxxxxxxxxxxxxxxxxxxxxxxx ================================================================== BUG: KCSAN: data-race in __filemap_add_folio / file_write_and_wait_range read-write to 0xffff888115692c60 of 8 bytes by task 14397 on cpu 0: __filemap_add_folio+0x430/0x6f0 mm/filemap.c:929 filemap_add_folio+0x9c/0x1b0 mm/filemap.c:981 __filemap_get_folio+0x32f/0x630 mm/filemap.c:1980 block_write_begin fs/buffer.c:2221 [inline] cont_write_begin+0x512/0x860 fs/buffer.c:2577 fat_write_begin+0x51/0xe0 fs/fat/inode.c:228 generic_perform_write+0x1a8/0x4a0 mm/filemap.c:4189 __generic_file_write_iter+0xa1/0x120 mm/filemap.c:4290 generic_file_write_iter+0x8f/0x310 mm/filemap.c:4316 new_sync_write fs/read_write.c:586 [inline] vfs_write+0x77b/0x920 fs/read_write.c:679 ksys_write+0xe8/0x1b0 fs/read_write.c:731 __do_sys_write fs/read_write.c:742 [inline] __se_sys_write fs/read_write.c:739 [inline] __x64_sys_write+0x42/0x50 fs/read_write.c:739 x64_sys_call+0x287e/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:2 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f read to 0xffff888115692c60 of 8 bytes by task 14402 on cpu 1: mapping_needs_writeback mm/filemap.c:644 [inline] file_write_and_wait_range+0x68/0x2f0 mm/filemap.c:796 __generic_file_fsync+0x46/0x140 fs/libfs.c:1525 fat_file_fsync+0x46/0x100 fs/fat/file.c:191 vfs_fsync_range fs/sync.c:187 [inline] vfs_fsync fs/sync.c:201 [inline] do_fsync fs/sync.c:212 [inline] __do_sys_fdatasync fs/sync.c:222 [inline] __se_sys_fdatasync fs/sync.c:220 [inline] __x64_sys_fdatasync+0x7e/0xd0 fs/sync.c:220 x64_sys_call+0x15e1/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:76 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f value changed: 0x0000000000000321 -> 0x0000000000000324 Reported by Kernel Concurrency Sanitizer on: CPU: 1 UID: 0 PID: 14402 Comm: syz.7.4702 Tainted: G W 6.14.0-rc3-syzkaller-00060-g6537cfb395f3 #0 Tainted: [W]=WARN Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024 ================================================================== --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup
