syzbot


KCSAN: data-race in __mark_inode_dirty / vfs_fsync_range (2)

Status: closed as invalid on 2020/06/18 14:13
Subsystems: ext4
[Documentation on labels]
First crash: 1686d, last: 1686d
Similar bugs (8)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in __mark_inode_dirty / vfs_fsync_range (6) exfat 1 1333d 1333d 0/28 auto-closed as invalid on 2021/07/10 17:50
upstream KCSAN: data-race in __mark_inode_dirty / vfs_fsync_range (9) ext4 2 121d 126d 0/28 auto-obsoleted due to no activity on 2024/11/03 13:13
upstream KCSAN: data-race in __mark_inode_dirty / vfs_fsync_range (5) ext4 5 1390d 1437d 0/28 auto-closed as invalid on 2021/05/14 12:10
upstream KCSAN: data-race in __mark_inode_dirty / vfs_fsync_range (4) ext4 6 1491d 1513d 0/28 auto-closed as invalid on 2021/02/02 16:23
upstream KCSAN: data-race in __mark_inode_dirty / vfs_fsync_range (8) exfat 1 435d 414d 0/28 auto-obsoleted due to no activity on 2023/12/26 00:02
upstream KCSAN: data-race in __mark_inode_dirty / vfs_fsync_range (7) ext4 1 630d 630d 0/28 auto-obsoleted due to no activity on 2023/06/13 15:21
upstream KCSAN: data-race in __mark_inode_dirty / vfs_fsync_range (3) ext4 1 1652d 1652d 0/28 auto-closed as invalid on 2020/08/25 18:47
upstream KCSAN: data-race in __mark_inode_dirty / vfs_fsync_range ext4 2 1922d 1924d 0/28 closed as invalid on 2019/11/19 13:44

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

write to 0xffff8880b69febc0 of 8 bytes by task 26745 on cpu 1:
 __mark_inode_dirty+0x5e6/0x940 fs/fs-writeback.c:2288
 generic_update_time+0x184/0x270 fs/inode.c:1682
 update_time+0x7d/0x90 fs/inode.c:1695
 file_update_time+0x205/0x2d0 fs/inode.c:1910
 file_modified fs/inode.c:1933 [inline]
 file_modified+0x60/0x80 fs/inode.c:1918
 ext4_write_checks+0x4a/0x70 fs/ext4/file.c:249
 ext4_buffered_write_iter+0x87/0x280 fs/ext4/file.c:265
 ext4_file_write_iter+0xf4/0xd30 fs/ext4/file.c:642
 call_write_iter include/linux/fs.h:1907 [inline]
 do_iter_readv_writev+0x4a7/0x5d0 fs/read_write.c:694
 do_iter_write fs/read_write.c:999 [inline]
 do_iter_write+0x137/0x3a0 fs/read_write.c:980
 vfs_iter_write+0x56/0x80 fs/read_write.c:1040
 iter_file_splice_write+0x530/0x830 fs/splice.c:760
 do_splice_from fs/splice.c:863 [inline]
 direct_splice_actor+0x97/0xb0 fs/splice.c:1037
 splice_direct_to_actor+0x22f/0x540 fs/splice.c:992
 do_splice_direct+0x152/0x1d0 fs/splice.c:1080
 do_sendfile+0x380/0x800 fs/read_write.c:1521
 __do_sys_sendfile64 fs/read_write.c:1576 [inline]
 __se_sys_sendfile64 fs/read_write.c:1568 [inline]
 __x64_sys_sendfile64+0xb8/0x140 fs/read_write.c:1568
 do_syscall_64+0xc7/0x3b0 arch/x86/entry/common.c:295
 entry_SYSCALL_64_after_hwframe+0x44/0xa9

read to 0xffff8880b69febc0 of 8 bytes by task 26794 on cpu 0:
 vfs_fsync_range+0xd3/0x150 fs/sync.c:195
 generic_write_sync include/linux/fs.h:2872 [inline]
 ext4_buffered_write_iter+0x211/0x280 fs/ext4/file.c:277
 ext4_file_write_iter+0xf4/0xd30 fs/ext4/file.c:642
 call_write_iter include/linux/fs.h:1907 [inline]
 do_iter_readv_writev+0x4a7/0x5d0 fs/read_write.c:694
 do_iter_write fs/read_write.c:999 [inline]
 do_iter_write+0x137/0x3a0 fs/read_write.c:980
 vfs_iter_write+0x56/0x80 fs/read_write.c:1040
 iter_file_splice_write+0x530/0x830 fs/splice.c:760
 do_splice_from fs/splice.c:863 [inline]
 direct_splice_actor+0x97/0xb0 fs/splice.c:1037
 splice_direct_to_actor+0x22f/0x540 fs/splice.c:992
 do_splice_direct+0x152/0x1d0 fs/splice.c:1080
 do_sendfile+0x380/0x800 fs/read_write.c:1521
 __do_sys_sendfile64 fs/read_write.c:1576 [inline]
 __se_sys_sendfile64 fs/read_write.c:1568 [inline]
 __x64_sys_sendfile64+0xb8/0x140 fs/read_write.c:1568
 do_syscall_64+0xc7/0x3b0 arch/x86/entry/common.c:295
 entry_SYSCALL_64_after_hwframe+0x44/0xa9

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 26794 Comm: syz-executor.2 Not tainted 5.7.0-rc1-syzkaller #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
2020/06/18 03:42 https://github.com/google/ktsan.git kcsan 7c3cd68e5d38 d45a4d69 .config console log report ci2-upstream-kcsan-gce
* Struck through repros no longer work on HEAD.