loop4: detected capacity change from 0 to 512
==================================================================
BUG: KCSAN: data-race in fsnotify_detach_mark / inotify_handle_inode_event

write to 0xffff888105744634 of 4 bytes by task 4845 on cpu 0:
 fsnotify_detach_mark+0xb9/0x160 fs/notify/mark.c:595
 fsnotify_destroy_mark+0x6f/0x150 fs/notify/mark.c:637
 __do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:806 [inline]
 __se_sys_inotify_rm_watch+0xe8/0x170 fs/notify/inotify/inotify_user.c:787
 __x64_sys_inotify_rm_watch+0x31/0x40 fs/notify/inotify/inotify_user.c:787
 x64_sys_call+0xc88/0x3020 arch/x86/include/generated/asm/syscalls_64.h:256
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x12c/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888105744634 of 4 bytes by task 5214 on cpu 1:
 inotify_handle_inode_event+0x34c/0x3d0 fs/notify/inotify/inotify_fsnotify.c:132
 fsnotify_handle_inode_event+0x1c0/0x220 fs/notify/fsnotify.c:272
 fsnotify_handle_event fs/notify/fsnotify.c:327 [inline]
 send_to_group fs/notify/fsnotify.c:375 [inline]
 fsnotify+0x15d0/0x1730 fs/notify/fsnotify.c:592
 __fsnotify_parent+0x2f8/0x3a0 fs/notify/fsnotify.c:238
 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:457 [inline]
 __fput+0x1de/0x630 fs/file_table.c:496
 fput_close_sync+0xad/0x190 fs/file_table.c:615
 __do_sys_close fs/open.c:1507 [inline]
 __se_sys_close fs/open.c:1492 [inline]
 __x64_sys_close+0x55/0xf0 fs/open.c:1492
 x64_sys_call+0x275d/0x3020 arch/x86/include/generated/asm/syscalls_64.h:4
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x12c/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00000003 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 5214 Comm: syz.4.520 Not tainted syzkaller #0 PREEMPT(lazy) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
==================================================================
EXT4-fs (loop4): mounting ext2 file system using the ext4 subsystem
EXT4-fs error (device loop4): ext4_orphan_get:1423: comm syz.4.520: bad orphan inode 15
loop4: lost filesystem error report for type 5 error -117
ext4_test_bit(bit=14, block=18) = 1
is_bad_inode(inode)=0
NEXT_ORPHAN(inode)=1023
max_ino=32
i_nlink=0
EXT4-fs error (device loop4): ext4_validate_block_bitmap:441: comm syz.4.520: bg 0: block 161: padding at end of block bitmap is not set
loop4: lost filesystem error report for type 5 error -117
EXT4-fs error (device loop4) in ext4_mb_clear_bb:6679: Corrupt filesystem
loop4: lost filesystem error report for type 5 error -117
EXT4-fs (loop4): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none.
ext2 filesystem being mounted at /86/éq‰Y’3aK supports timestamps until 2038-01-19 (0x7fffffff)