Hello,
syzbot found the following issue on:
HEAD commit: 2a8120d7b482 Merge tag 's390-6.10-2' of git://git.kernel.o..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=11166c44980000
kernel config:
https://syzkaller.appspot.com/x/.config?x=f35bb3f898275bfc
dashboard link:
https://syzkaller.appspot.com/bug?extid=8e392ba0f2f77b424b3f
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/c7fb0632f985/disk-2a8120d7.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/78cc88e198bf/vmlinux-2a8120d7.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/79a49ed243be/bzImage-2a8120d7.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+8e392b...@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in fsnotify_event_needs_parent / fsnotify_put_mark
write to 0xffff88810122e034 of 4 bytes by task 3075 on cpu 0:
fsnotify_detach_connector_from_object fs/notify/mark.c:304 [inline]
fsnotify_put_mark+0x2d8/0x5d0 fs/notify/mark.c:367
__do_sys_inotify_rm_watch fs/notify/inotify/inotify_user.c:819 [inline]
__se_sys_inotify_rm_watch+0x105/0x180 fs/notify/inotify/inotify_user.c:793
__x64_sys_inotify_rm_watch+0x31/0x40 fs/notify/inotify/inotify_user.c:793
x64_sys_call+0x2735/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:256
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+0x77/0x7f
read to 0xffff88810122e034 of 4 bytes by task 4392 on cpu 1:
fsnotify_event_needs_parent+0x47/0x100 fs/notify/fsnotify.c:175
__fsnotify_parent+0x178/0x370 fs/notify/fsnotify.c:222
fsnotify_parent include/linux/fsnotify.h:96 [inline]
fsnotify_file include/linux/fsnotify.h:125 [inline]
fsnotify_close include/linux/fsnotify.h:406 [inline]
__fput+0x1f7/0x660 fs/file_table.c:408
__fput_sync+0x44/0x60 fs/file_table.c:507
__do_sys_close fs/open.c:1556 [inline]
__se_sys_close+0x101/0x1b0 fs/open.c:1541
__x64_sys_close+0x1f/0x30 fs/open.c:1541
x64_sys_call+0x25b9/0x2d30 arch/x86/include/generated/asm/syscalls_64.h:4
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+0x77/0x7f
value changed: 0x00002008 -> 0x00000000
Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 4392 Comm: syz-executor.2 Not tainted 6.9.0-syzkaller-10713-g2a8120d7b482 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/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