syzbot


KCSAN: data-race in __writeback_single_inode / vfs_fsync_range (7)

Status: auto-closed as invalid on 2022/04/13 08:14
Subsystems: exfat
[Documentation on labels]
First crash: 925d, last: 925d
Similar bugs (8)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in __writeback_single_inode / vfs_fsync_range ext4 2 1775d 1777d 0/28 closed as invalid on 2019/11/19 14:44
upstream KCSAN: data-race in __writeback_single_inode / vfs_fsync_range (6) ext4 1 1241d 1241d 0/28 auto-closed as invalid on 2021/06/01 07:24
upstream KCSAN: data-race in __writeback_single_inode / vfs_fsync_range (8) ext4 exfat 2 613d 620d 0/28 auto-obsoleted due to no activity on 2023/04/01 19:00
upstream KCSAN: data-race in __writeback_single_inode / vfs_fsync_range (5) exfat 2 1318d 1335d 0/28 auto-closed as invalid on 2021/03/15 14:17
upstream KCSAN: data-race in __writeback_single_inode / vfs_fsync_range (9) ext4 2 5d17h 9d18h 0/28 moderation: reported on 2024/09/09 18:07
upstream KCSAN: data-race in __writeback_single_inode / vfs_fsync_range (3) ext4 2 1513d 1540d 0/28 auto-closed as invalid on 2020/09/02 05:07
upstream KCSAN: data-race in __writeback_single_inode / vfs_fsync_range (2) ext4 2 1751d 1752d 0/28 auto-closed as invalid on 2020/02/12 06:26
upstream KCSAN: data-race in __writeback_single_inode / vfs_fsync_range (4) ext4 1 1473d 1473d 0/28 auto-closed as invalid on 2020/10/12 03:20

Sample crash report:
==================================================================
BUG: KCSAN: data-race in __writeback_single_inode / vfs_fsync_range

write to 0xffff888133dc1160 of 8 bytes by task 4138 on cpu 0:
 __writeback_single_inode+0x1ed/0x590 fs/fs-writeback.c:1654
 writeback_single_inode+0x11f/0x3d0 fs/fs-writeback.c:1739
 sync_inode_metadata+0x59/0x80 fs/fs-writeback.c:2759
 __generic_file_fsync+0xf5/0x140 fs/libfs.c:1126
 fat_file_fsync+0x48/0x100 fs/fat/file.c:191
 vfs_fsync_range+0x107/0x120 fs/sync.c:188
 generic_write_sync include/linux/fs.h:2884 [inline]
 generic_file_write_iter+0x103/0x130 mm/filemap.c:3928
 call_write_iter include/linux/fs.h:2074 [inline]
 do_iter_readv_writev+0x2de/0x380 fs/read_write.c:725
 do_iter_write+0x192/0x5c0 fs/read_write.c:851
 vfs_iter_write+0x4c/0x70 fs/read_write.c:892
 iter_file_splice_write+0x43a/0x790 fs/splice.c:689
 do_splice_from fs/splice.c:767 [inline]
 direct_splice_actor+0x80/0xa0 fs/splice.c:936
 splice_direct_to_actor+0x345/0x650 fs/splice.c:891
 do_splice_direct+0x106/0x190 fs/splice.c:979
 do_sendfile+0x675/0xc40 fs/read_write.c:1245
 __do_sys_sendfile64 fs/read_write.c:1304 [inline]
 __se_sys_sendfile64 fs/read_write.c:1296 [inline]
 __x64_sys_sendfile64+0xb9/0x140 fs/read_write.c:1296
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888133dc1160 of 8 bytes by task 4205 on cpu 1:
 vfs_fsync_range+0x98/0x120 fs/sync.c:186
 generic_write_sync include/linux/fs.h:2884 [inline]
 generic_file_write_iter+0x103/0x130 mm/filemap.c:3928
 call_write_iter include/linux/fs.h:2074 [inline]
 do_iter_readv_writev+0x2de/0x380 fs/read_write.c:725
 do_iter_write+0x192/0x5c0 fs/read_write.c:851
 vfs_iter_write+0x4c/0x70 fs/read_write.c:892
 iter_file_splice_write+0x43a/0x790 fs/splice.c:689
 do_splice_from fs/splice.c:767 [inline]
 direct_splice_actor+0x80/0xa0 fs/splice.c:936
 splice_direct_to_actor+0x345/0x650 fs/splice.c:891
 do_splice_direct+0x106/0x190 fs/splice.c:979
 do_sendfile+0x675/0xc40 fs/read_write.c:1245
 __do_sys_sendfile64 fs/read_write.c:1304 [inline]
 __se_sys_sendfile64 fs/read_write.c:1296 [inline]
 __x64_sys_sendfile64+0xb9/0x140 fs/read_write.c:1296
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x0000000000000087 -> 0x0000000000000084

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 4205 Comm: syz-executor.2 Not tainted 5.17.0-rc7-syzkaller-00060-g92f90cc9fe0e-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/03/09 08:05 upstream 92f90cc9fe0e 9e8eaa75 .config console log report info ci2-upstream-kcsan-gce KCSAN: data-race in __writeback_single_inode / vfs_fsync_range
* Struck through repros no longer work on HEAD.