==================================================================
BUG: KCSAN: data-race in fsnotify_detach_mark / fsnotify_handle_inode_event

write to 0xffff8881058ac404 of 4 bytes by task 10728 on cpu 1:
 fsnotify_detach_mark+0xb9/0x160 fs/notify/mark.c:624
 fsnotify_destroy_mark+0x6a/0x140 fs/notify/mark.c:666
 __do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:793 [inline]
 __se_sys_inotify_rm_watch+0xe8/0x170 fs/notify/inotify/inotify_user.c:774
 __x64_sys_inotify_rm_watch+0x31/0x40 fs/notify/inotify/inotify_user.c:774
 x64_sys_call+0x1f51/0x2550 arch/x86/include/generated/asm/syscalls_64.h:256
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x116/0x380 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff8881058ac404 of 4 bytes by task 11105 on cpu 0:
 fsnotify_handle_inode_event+0x13d/0x230 fs/notify/fsnotify.c:267
 fsnotify_handle_event fs/notify/fsnotify.c:330 [inline]
 send_to_group fs/notify/fsnotify.c:378 [inline]
 fsnotify+0x16ae/0x1860 fs/notify/fsnotify.c:597
 __fsnotify_parent+0x2f8/0x3a0 fs/notify/fsnotify.c:241
 fsnotify_parent include/linux/fsnotify.h:96 [inline]
 fsnotify_path include/linux/fsnotify.h:113 [inline]
 fsnotify_file include/linux/fsnotify.h:127 [inline]
 fsnotify_close include/linux/fsnotify.h:461 [inline]
 __fput+0x1cb/0x610 fs/file_table.c:498
 fput_close_sync+0xad/0x190 fs/file_table.c:618
 filp_close_sync fs/open.c:1574 [inline]
 __do_sys_close fs/open.c:1597 [inline]
 __se_sys_close fs/open.c:1584 [inline]
 __x64_sys_close+0x55/0xf0 fs/open.c:1584
 x64_sys_call+0x812/0x2550 arch/x86/include/generated/asm/syscalls_64.h:4
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x116/0x380 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00000003 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 11105 Comm: syz.4.2278 Not tainted syzkaller #0 PREEMPT(lazy) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
==================================================================
EXT4-fs (loop4): feature flags set on rev 0 fs, running e2fsck is recommended
EXT4-fs (loop4): mounting ext2 file system using the ext4 subsystem
EXT4-fs (loop4): warning: checktime reached, running e2fsck is recommended
[EXT4 FS bs=4096, gc=1, bpg=32768, ipg=32, mo=a042c01c, mo2=0002]
System zones: 0-2, 18-18, 34-34
EXT4-fs error (device loop4): ext4_orphan_get:1404: comm syz.4.2278: inode #15: comm syz.4.2278: iget: illegal inode #
loop4: lost filesystem error report for type 5 error -117
EXT4-fs error (device loop4): ext4_orphan_get:1409: comm syz.4.2278: couldn't read orphan inode 15 (err -117)
loop4: lost filesystem error report for type 5 error -117
EXT4-fs error (device loop4): ext4_search_dir:1476: inode #2: block 3: comm syz.4.2278: bad entry in directory: directory entry overrun - offset=44, inode=262156, rec_len=4096, size=4096 fake=0