Hello,
syzbot found the following issue on:
HEAD commit: 20eef29b7c84 Merge tag 'arc-fixes-7.4' of git://git.kernel..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=1562c3a1580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=1c70adb69e647dcc
dashboard link:
https://syzkaller.appspot.com/bug?extid=76819c64ceed92d01ea7
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
CC: [
bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/322d6104232e/disk-20eef29b.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/6355393bc114/vmlinux-20eef29b.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/2d4bcbb4bcc7/bzImage-20eef29b.xz
AI-generated root cause summary:
A data race reported by KCSAN occurs on pipe->writers between anon_pipe_read()
and pipe_release(). While waiting for data, anon_pipe_read() drops pipe->mutex
and evaluates pipe_readable(), which executes a lockless marked read
READ_ONCE(pipe->writers). Concurrently, a closing writer in pipe_release()
decrements the counter under pipe->mutex using an unmarked plain write
(pipe->writers--), violating the Linux Kernel Memory Model rule that concurrent
plain writes to variables read locklessly without locks must be annotated with
WRITE_ONCE().
full analysis:
https://syzkaller.appspot.com/x/ai_root_cause?x=76819c64ceed92d01ea7
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+76819c...@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in anon_pipe_read / pipe_release
read (marked) to 0xffff88811c366060 of 4 bytes by task 6895 on cpu 1:
pipe_readable fs/pipe.c:265 [inline]
anon_pipe_read+0x54f/0x9b0 fs/pipe.c:420
new_sync_read fs/read_write.c:473 [inline]
vfs_read+0x6ac/0x7d0 fs/read_write.c:554
ksys_read+0xdc/0x1a0 fs/read_write.c:696
__do_sys_read fs/read_write.c:705 [inline]
__se_sys_read fs/read_write.c:703 [inline]
__x64_sys_read+0x40/0x50 fs/read_write.c:703
x64_sys_call+0x2135/0x2550 arch/x86/include/generated/asm/syscalls_64.h:1
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x11e/0x3a0 arch/x86/entry/syscall_64.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
write to 0xffff88811c366060 of 4 bytes by task 6924 on cpu 0:
pipe_release+0xb6/0x1d0 fs/pipe.c:773
__fput+0x292/0x660 fs/file_table.c:512
fput_close_sync+0xd5/0x1d0 fs/file_table.c:618
filp_close_sync+0x27/0x40 fs/open.c:1574
close_files fs/file.c:572 [inline]
put_files_struct+0x11a/0x1e0 fs/file.c:584
switch_files_struct fs/file.c:598 [inline]
exit_files+0x6a/0x80 fs/file.c:604
do_exit+0x492/0x1530 kernel/exit.c:977
do_group_exit+0x138/0x140 kernel/exit.c:1123
__do_sys_exit_group kernel/exit.c:1134 [inline]
__se_sys_exit_group kernel/exit.c:1132 [inline]
__x64_sys_exit_group+0x1f/0x20 kernel/exit.c:1132
x64_sys_call+0x254f/0x2550 arch/x86/include/generated/asm/syscalls_64.h:232
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x11e/0x3a0 arch/x86/entry/syscall_64.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 6924 Comm: dhcpcd-run-hook Not tainted syzkaller #0 PREEMPT(lazy)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
==================================================================
---
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