[v6.1] SYZFAIL: vendor_pkt_req write failed (2)

3 views
Skip to first unread message

syzbot

unread,
Jul 28, 2025, 6:28:40 PMJul 28
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3594f306da12 Linux 6.1.147
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12d494a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2be97b627a5d7554
dashboard link: https://syzkaller.appspot.com/bug?extid=a70991610b585e59018f
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0d2a884e198e/disk-3594f306.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/23d3643328c7/vmlinux-3594f306.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ef83d78711e3/Image-3594f306.gz.xz

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

SYZFAIL: vendor_pkt_req write failed
(errno 77: File descriptor in bad state)
loop exited with status 67
SYZFAIL: repeatedly failed to execute the program
proc=6 req=181 state=1 status=9 (errno 11: Resource temporarily unavailable)


---
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,
Nov 5, 2025, 5:28:21 PM (yesterday) Nov 5
to syzkaller...@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