SYZFAIL: too many calls in output (2)

7 views
Skip to first unread message

syzbot

unread,
Feb 7, 2025, 3:41:29 AM2/7/25
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3dd691bf9970 sys/uvideo: add quriks for Elgato Game Captur..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=17c8e4a4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=851348deb22366fdc793

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cbd07261d2d1/disk-3dd691bf.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/53e5106b2ada/bsd-3dd691bf.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5158f0d541ec/kernel-3dd691bf.xz

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

��1! �Go_�cMB“�R���iQ��]�,�/h���� j Q�� k"P� ./file0 � � ����{ SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: Undefined error: 0)
ifconfig: tap5: SIOCIFDESTROY: Device not configured
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: Undefined error: 0)
ifconfig: tap5: SIOCIFDESTROY: Device not configured
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: Undefined error: 0)
ifconfig: tap5: SIOCIFDESTROY: Device not configured
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFAIL: child failed
(errno 0: Undefined error: 0)
ifconfig: tap5: SIOCIFDESTROY: Device not configured
SYZFAIL: too many calls in output
slot=64 (errno 1: Operation not permitted)
SYZFA

---
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,
May 29, 2026, 3:00:15 PMMay 29
to syzkaller-o...@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