[moderation] [fs?] KCSAN: data-race in fsnotify_destroy_mark / fsnotify_handle_inode_event (5)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 047371968ffc Merge tag 'v6.8-p3' of git://git.kernel.org/p..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=111a9cbfe80000
kernel config: https://syzkaller.appspot.com/x/.config?x=3cd0dc1b46a5bc5c
dashboard link: https://syzkaller.appspot.com/bug?extid=6b63a49c4822f9638fcb
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [amir...@gmail.com ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c52200287356/disk-04737196.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/820016a9b91b/vmlinux-04737196.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f66a09c33ecf/bzImage-04737196.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6b63a4...@syzkaller.appspotmail.com

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

write to 0xffff888103fbd724 of 4 bytes by task 20038 on cpu 0:
fsnotify_free_mark fs/notify/mark.c:481 [inline]
fsnotify_destroy_mark+0x146/0x190 fs/notify/mark.c:499
__do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:816 [inline]
__se_sys_inotify_rm_watch+0xfd/0x180 fs/notify/inotify/inotify_user.c:793
__x64_sys_inotify_rm_watch+0x31/0x40 fs/notify/inotify/inotify_user.c:793
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff888103fbd724 of 4 bytes by task 30605 on cpu 1:
fsnotify_handle_inode_event+0xfa/0x200 fs/notify/fsnotify.c:256
fsnotify_handle_event fs/notify/fsnotify.c:316 [inline]
send_to_group fs/notify/fsnotify.c:364 [inline]
fsnotify+0x101d/0x1150 fs/notify/fsnotify.c:570
__fsnotify_parent+0x307/0x480 fs/notify/fsnotify.c:230
fsnotify_parent include/linux/fsnotify.h:77 [inline]
fsnotify_file include/linux/fsnotify.h:100 [inline]
fsnotify_close include/linux/fsnotify.h:381 [inline]
__fput+0x1da/0x630 fs/file_table.c:362
__fput_sync+0x44/0x50 fs/file_table.c:461
__do_sys_close fs/open.c:1554 [inline]
__se_sys_close+0xfa/0x1a0 fs/open.c:1539
__x64_sys_close+0x1f/0x30 fs/open.c:1539
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x00000001 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 30605 Comm: syz-executor.0 Not tainted 6.8.0-rc3-syzkaller-00047-g047371968ffc #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
==================================================================


---
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 syzk...@googlegroups.com.

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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.