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

write to 0xffff88816ffdd634 of 4 bytes by task 5601 on cpu 0:
 fsnotify_detach_mark+0xb9/0x160 fs/notify/mark.c:558
 fsnotify_destroy_mark+0x6f/0x150 fs/notify/mark.c:600
 __do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:805 [inline]
 __se_sys_inotify_rm_watch+0xe8/0x170 fs/notify/inotify/inotify_user.c:786
 __x64_sys_inotify_rm_watch+0x31/0x40 fs/notify/inotify/inotify_user.c:786
 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/0x370 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88816ffdd634 of 4 bytes by task 6527 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/0x650 fs/file_table.c:455
 fput_close_sync+0xad/0x190 fs/file_table.c:574
 __do_sys_close fs/open.c:1509 [inline]
 __se_sys_close fs/open.c:1494 [inline]
 __x64_sys_close+0x55/0xf0 fs/open.c:1494
 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/0x370 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: 6527 Comm: syz.9.7649 Tainted: G        W           syzkaller #0 PREEMPT(full) 
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
==================================================================
EXT4-fs (loop9): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop9): 1 truncate cleaned up
EXT4-fs (loop9): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none.
EXT4-fs error (device loop9): ext4_generic_delete_entry:2666: inode #2: block 13: comm syz.9.7649: bad entry in directory: rec_len is smaller than minimal - offset=24, inode=11, rec_len=8, size=1024 fake=0
EXT4-fs (loop9): Remounting filesystem read-only
EXT4-fs warning (device loop9): ext4_rename_delete:3729: inode #2: comm syz.9.7649: Deleting old file: nlink 4, error=-117