[moderation] [fs?] KCSAN: data-race in fsnotify_detach_mark / inotify_handle_inode_event (2)

Hello,

syzbot found the following issue on:

HEAD commit: 7234e2ea0edd Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=139e8440580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a2f7ae2f221e9eae
dashboard link: https://syzkaller.appspot.com/bug?extid=b843bae81ed3042a49b9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [[email protected] [email protected] [email protected] [email protected]]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9727ab4b5b6e/disk-7234e2ea.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2dcfb89765d7/vmlinux-7234e2ea.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6a7f14058d0c/bzImage-7234e2ea.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

loop1: detected capacity change from 0 to 512
EXT4-fs (loop1): couldn't mount as ext2 due to feature incompatibilities
loop1: detected capacity change from 0 to 512
==================================================================
BUG: KCSAN: data-race in fsnotify_detach_mark / inotify_handle_inode_event

write to 0xffff888103fe2b34 of 4 bytes by task 6326 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 0xffff888103fe2b34 of 4 bytes by task 13559 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:1565 [inline]
__se_sys_close+0xf9/0x1a0 fs/open.c:1550
__x64_sys_close+0x1f/0x30 fs/open.c:1550
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: 13559 Comm: syz.1.2944 Not tainted 6.12.0-rc2-syzkaller-00305-g7234e2ea0edd #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
==================================================================
netlink: 60 bytes leftover after parsing attributes in process `syz.1.2944'.


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at [email protected].

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup