[v6.1] SYZFAIL: proc stdout read failed (2)

0 views
Skip to first unread message

syzbot

unread,
Sep 27, 2025, 1:23:36 AM (11 days ago) Sep 27
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 7b34dc04e4ff Linux 6.1.154
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=115c02e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=f20ff0cdf0d38e702b2f
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1f1ed5df43e0/disk-7b34dc04.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/941b7c0f58be/vmlinux-7b34dc04.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6fb9bad299e4/bzImage-7b34dc04.xz

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

SYZFAIL: proc stdout read failed
(errno 61: No data available)


---
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
Reply all
Reply to author
Forward
0 new messages