SYZFAIL: tun: read failed (2)

1 view
Skip to first unread message

syzbot

unread,
Sep 23, 2021, 10:45:31 PM9/23/21
to syzkaller-f...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 5572fda3a2f3 mvneta: split to FDT and generic part
git tree: https://github.com/freebsd/freebsd-src.git main
console output: https://syzkaller.appspot.com/x/log.txt?x=10d4016f300000
dashboard link: https://syzkaller.appspot.com/bug?extid=377efc3b288907cac2b9
userspace arch: i386

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

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

SYZFAIL: tun: read failed
(errno 19: Operation not supported by device)
SYZFAIL: child failed
(errno 0: No error: 0)
if_delmulti_locked: detaching ifnet instance 0xfffffe0058821000
if_delmulti_locked: detaching ifnet instance 0xfffffe0058821000
if_delmulti_locked: detaching ifnet instance 0xfffffe0058821000
if_delmulti_locked: detaching ifnet instance 0xfffffe0058821000
if_delmulti_locked: detaching ifnet instance 0xfffffe0058821000
if_delmulti_locked: detaching ifnet instance 0xfffffe0058821000
if_delmulti_locked: detaching ifnet instance 0xfffffe00587fa800
if_delmulti_locked: detaching ifnet instance 0xfffffe00587fa800
if_delmulti_locked: detaching ifnet instance 0xfffffe00587fa800
Sep 24 02:44:42 ci-freebsd-i386-3 dhclient[56398]: Interface tap3 is down, dhclient exiting
if_delmulti_locked: detaching ifnet instance 0xfffffe005881f000
if_delmulti_locked: detaching ifnet instance 0xfffffe005881f000
if_delmulti_locked: detaching ifnet instance 0xfffffe00588
1f000

FreeBSD/amd64 (ci-freebsd-i386-3.c.syzkaller.internal) (ttyu0)

login: Sep 24 02:44:42 ci-freebsd-i386-3 dhclient[61435]: Interface tap0 is down, dhclient exitin


---
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.

syzbot

unread,
Jan 25, 2022, 4:19:14 AM1/25/22
to syzkaller-f...@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