syzbot


KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event (4)

Status: auto-obsoleted due to no activity on 2024/01/03 04:57
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+f9804f11cf999829b865@syzkaller.appspotmail.com
First crash: 162d, last: 162d
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event (5) fs 2 71d 90d 0/26 auto-obsoleted due to no activity on 2024/04/02 20:17
upstream KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event fs 1 305d 305d 0/26 auto-obsoleted due to no activity on 2023/08/13 07:22
upstream KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event (3) fs 2 220d 223d 0/26 auto-obsoleted due to no activity on 2023/11/05 21:43
upstream KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event (2) fs 1 262d 262d 0/26 auto-obsoleted due to no activity on 2023/09/24 11:29

Sample crash report:
loop5: detected capacity change from 0 to 512
EXT4-fs (loop5): unable to read superblock
==================================================================
BUG: KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event

write to 0xffff888103b8e0e4 of 4 bytes by task 28795 on cpu 0:
 fsnotify_free_mark fs/notify/mark.c:481 [inline]
 fsnotify_destroy_mark+0x146/0x190 fs/notify/mark.c:499
 __do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:817 [inline]
 __se_sys_inotify_rm_watch+0xfd/0x180 fs/notify/inotify/inotify_user.c:794
 __x64_sys_inotify_rm_watch+0x31/0x40 fs/notify/inotify/inotify_user.c:794
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
 entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff888103b8e0e4 of 4 bytes by task 6978 on cpu 1:
 fsnotify_handle_inode_event+0xfa/0x1f0 fs/notify/fsnotify.c:256
 fsnotify_handle_event fs/notify/fsnotify.c:316 [inline]
 send_to_group fs/notify/fsnotify.c:364 [inline]
 fsnotify+0x101c/0x1150 fs/notify/fsnotify.c:570
 __fsnotify_parent+0x307/0x480 fs/notify/fsnotify.c:230
 fsnotify_parent include/linux/fsnotify.h:77 [inline]
 fsnotify_file include/linux/fsnotify.h:100 [inline]
 fsnotify_close include/linux/fsnotify.h:342 [inline]
 __fput+0x1da/0x630 fs/file_table.c:380
 __fput_sync+0x44/0x50 fs/file_table.c:475
 __do_sys_close fs/open.c:1590 [inline]
 __se_sys_close+0xfa/0x1a0 fs/open.c:1575
 __x64_sys_close+0x1f/0x30 fs/open.c:1575
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
 entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x00000001 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 6978 Comm: syz-executor.5 Not tainted 6.7.0-rc3-syzkaller-00024-g18d46e76d7c2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/11/29 04:56 upstream 18d46e76d7c2 1adfb6f6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event
* Struck through repros no longer work on HEAD.