[v6.1] SYZFAIL: tun: can't open /dev/net/tun

0 views
Skip to first unread message

syzbot

unread,
Nov 30, 2023, 12:11:23 PM11/30/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6ac30d748bb0 Linux 6.1.64
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=108ef52ce80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d9d5b8fc77ddec1d
dashboard link: https://syzkaller.appspot.com/bug?extid=d9ddbcc6a2f766478ff7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=136d468ce80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/44d935903e58/disk-6ac30d74.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4ab15c3e6cf0/vmlinux-6ac30d74.xz
kernel image: https://storage.googleapis.com/syzbot-assets/685a454f5bd1/bzImage-6ac30d74.xz

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

2023/11/30 16:54:02 [FATAL] executor failed 11 times: executor 5: failed to write control pipe: write |1: broken pipe
SYZFAIL: tun: can't open /dev/net/tun
(errno 2: No such file or directory)
loop exited with 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 report is already addressed, 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 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