[moderation] [fs?] KCSAN: data-race in fsnotify_destroy_mark / inotify_handle_inode_event (8)

5 views
Skip to first unread message

syzbot

unread,
Jan 29, 2025, 9:07:23 PM1/29/25
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ebbb8be421ee Merge tag 'regulator-fix-v6.14-merge-window' ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15537918580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ecaa299678460f3d
dashboard link: https://syzkaller.appspot.com/bug?extid=a8a59515adec76e1f33b
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/725bfca839a1/disk-ebbb8be4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4f47d34c5af4/vmlinux-ebbb8be4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c88ba49d1a4f/bzImage-ebbb8be4.xz

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

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

write to 0xffff88812784da44 of 4 bytes by task 3673 on cpu 1:
fsnotify_free_mark fs/notify/mark.c:573 [inline]
fsnotify_destroy_mark+0xe8/0x140 fs/notify/mark.c:591
__do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:805 [inline]
__se_sys_inotify_rm_watch+0xea/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+0x25e0/0x2dc0 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 0xffff88812784da44 of 4 bytes by task 4344 on cpu 0:
inotify_handle_inode_event+0x2d8/0x320 fs/notify/inotify/inotify_fsnotify.c:132
fsnotify_handle_inode_event+0x1bd/0x220 fs/notify/fsnotify.c:316
fsnotify_handle_event fs/notify/fsnotify.c:371 [inline]
send_to_group fs/notify/fsnotify.c:419 [inline]
fsnotify+0x1187/0x1260 fs/notify/fsnotify.c:628
__fsnotify_parent+0x2f5/0x340 fs/notify/fsnotify.c:282
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:456 [inline]
__fput+0x1e7/0x640 fs/file_table.c:436
__fput_sync+0x96/0xc0 fs/file_table.c:536
__do_sys_close fs/open.c:1579 [inline]
__se_sys_close fs/open.c:1564 [inline]
__x64_sys_close+0x55/0xe0 fs/open.c:1564
x64_sys_call+0x266c/0x2dc0 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: 0x00000001 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 4344 Comm: syz.3.282 Not tainted 6.13.0-syzkaller-09383-gebbb8be421ee #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/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

unread,
Mar 26, 2025, 10:07:21 PM3/26/25
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages