[v6.1] SYZFAIL: tun read failed

1 view
Skip to first unread message

syzbot

unread,
Oct 31, 2023, 12:06:28 AM10/31/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 32c9cdbe383c Linux 6.1.60
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1080f31b680000
kernel config: https://syzkaller.appspot.com/x/.config?x=c022d971b9287d2b
dashboard link: https://syzkaller.appspot.com/bug?extid=38532ebe274fa8ad9ba9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1137f86f680000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a490a5ba6b9d/disk-32c9cdbe.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2c65d1af9e04/vmlinux-32c9cdbe.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d262499bca4d/Image-32c9cdbe.gz.xz

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

1970/01/01 00:04:08 [FATAL] executor failed 11 times: executor 0: exit status 67 err exit status 67
SYZFAIL: tun read failed
(errno 9: Bad file descriptor)
SYZFAIL: child failed
(errno 0: Success)
loop exited with status 67
exit status 67

SYZFAIL: tun read failed
(errno 9: Bad file descriptor)
SYZFAIL: child failed
(errno 0: Success)
loop exited with status 67
exit status 67


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, 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