syzbot

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

write to 0xffff8881044b7db4 of 4 bytes by task 3905 on cpu 1:
 fsnotify_detach_mark+0xba/0x160 fs/notify/mark.c:541
 fsnotify_destroy_mark+0x6e/0x140 fs/notify/mark.c:583
 __do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:816 [inline]
 __se_sys_inotify_rm_watch+0xf1/0x170 fs/notify/inotify/inotify_user.c:793
 __x64_sys_inotify_rm_watch+0x31/0x40 fs/notify/inotify/inotify_user.c:793
 x64_sys_call+0x1ae0/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:256
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff8881044b7db4 of 4 bytes by task 4940 on cpu 0:
 inotify_handle_inode_event+0x2c2/0x310 fs/notify/inotify/inotify_fsnotify.c:132
 fsnotify_handle_inode_event+0x18e/0x1f0 fs/notify/fsnotify.c:298
 fsnotify_handle_event fs/notify/fsnotify.c:350 [inline]
 send_to_group fs/notify/fsnotify.c:398 [inline]
 fsnotify+0x10b0/0x11a0 fs/notify/fsnotify.c:607
 __fsnotify_parent+0x285/0x380 fs/notify/fsnotify.c:264
 fsnotify_parent include/linux/fsnotify.h:96 [inline]
 fsnotify_file include/linux/fsnotify.h:131 [inline]
 fsnotify_close include/linux/fsnotify.h:412 [inline]
 __fput+0x5a6/0x6d0 fs/file_table.c:417
 __fput_sync+0x43/0x60 fs/file_table.c:516
 __do_sys_close fs/open.c:1567 [inline]
 __se_sys_close+0xf9/0x1a0 fs/open.c:1552
 __x64_sys_close+0x1f/0x30 fs/open.c:1552
 x64_sys_call+0x25cb/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:4
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00000003 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 4940 Comm: syz.3.567 Not tainted 6.12.0-rc7-syzkaller-00189-ge8bdb3c8be08 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
==================================================================
EXT4-fs (loop3): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: writeback.
ext4 filesystem being mounted at /105/file0 supports timestamps until 2038-01-19 (0x7fffffff)
EXT4-fs error (device loop3): ext4_do_update_inode:5121: inode #18: comm syz.3.567: corrupted inode contents
EXT4-fs error (device loop3): ext4_dirty_inode:5984: inode #18: comm syz.3.567: mark_inode_dirty error
EXT4-fs error (device loop3): ext4_do_update_inode:5121: inode #18: comm syz.3.567: corrupted inode contents
EXT4-fs error (device loop3): ext4_xattr_delete_inode:3006: inode #18: comm syz.3.567: mark_inode_dirty error
EXT4-fs error (device loop3): ext4_xattr_delete_inode:3009: inode #18: comm syz.3.567: mark inode dirty (error -117)
EXT4-fs warning (device loop3): ext4_evict_inode:276: xattr delete (err -117)