syzbot


KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (6)

Status: moderation: reported on 2024/04/09 13:13
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+72b0ce21c4170d6a277e@syzkaller.appspotmail.com
First crash: 20d, last: 20d
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event fs 1 636d 636d 0/26 auto-closed as invalid on 2022/09/07 06:46
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (4) fs 1 281d 281d 0/26 auto-obsoleted due to no activity on 2023/08/27 10:05
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (2) fs 1 541d 541d 0/26 auto-obsoleted due to no activity on 2022/12/10 20:40
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (3) fs 1 388d 388d 0/26 auto-obsoleted due to no activity on 2023/05/12 13:04
upstream KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (5) fs 3 182d 193d 0/26 auto-obsoleted due to no activity on 2023/12/04 18:59

Sample crash report:
==================================================================
BUG: KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event

write to 0xffff88810ee0b594 of 4 bytes by task 21058 on cpu 1:
 fsnotify_free_mark fs/notify/mark.c:481 [inline]
 fsnotify_destroy_mark+0x146/0x1a0 fs/notify/mark.c:499
 __do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:816 [inline]
 __se_sys_inotify_rm_watch+0xfd/0x180 fs/notify/inotify/inotify_user.c:793
 __x64_sys_inotify_rm_watch+0x31/0x40 fs/notify/inotify/inotify_user.c:793
 do_syscall_64+0xd3/0x1d0
 entry_SYSCALL_64_after_hwframe+0x72/0x7a

read to 0xffff88810ee0b594 of 4 bytes by task 16401 on cpu 0:
 inotify_handle_inode_event+0x2c7/0x310 fs/notify/inotify/inotify_fsnotify.c:132
 fsnotify_handle_inode_event+0x18e/0x1f0 fs/notify/fsnotify.c:270
 fsnotify_handle_event fs/notify/fsnotify.c:322 [inline]
 send_to_group fs/notify/fsnotify.c:370 [inline]
 fsnotify+0x1023/0x1160 fs/notify/fsnotify.c:576
 __fsnotify_parent+0x285/0x370 fs/notify/fsnotify.c:236
 fsnotify_parent include/linux/fsnotify.h:83 [inline]
 fsnotify_file include/linux/fsnotify.h:106 [inline]
 fsnotify_close include/linux/fsnotify.h:387 [inline]
 __fput+0x1ff/0x660 fs/file_table.c:408
 __fput_sync+0x44/0x60 fs/file_table.c:507
 __do_sys_close fs/open.c:1556 [inline]
 __se_sys_close+0x101/0x1b0 fs/open.c:1541
 __x64_sys_close+0x1f/0x30 fs/open.c:1541
 do_syscall_64+0xd3/0x1d0
 entry_SYSCALL_64_after_hwframe+0x72/0x7a

value changed: 0x00000001 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 16401 Comm: syz-executor.0 Tainted: G        W          6.9.0-rc3-syzkaller-00011-g20cb38a7af88 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
==================================================================
EXT4-fs (loop0): unmounting filesystem 00000000-0000-0000-0000-000000000000.

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/09 13:12 upstream 20cb38a7af88 f3234354 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event
* Struck through repros no longer work on HEAD.