SYZFAIL: tun: can't open device (6)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cb7d86176520 regen
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=12d32182580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=39360db8516b9e181809

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/37d3272ee70d/disk-cb7d8617.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/e235daa7371a/bsd-cb7d8617.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/857cb30a0002/kernel-cb7d8617.xz

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

SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
SYZFAIL: ioctl remote attach failed
(errno 16: Device busy)
SYZFAIL: ioctl remote attach failed
(errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap6 (errno 16: Device busy)
SYZFAIL: repeatedly failed to execute the program
proc=6 req=7 state=1 status=67 (errno 4: Interrupted system call)
56. &,53(: /"*=08&&&&&$806#6#4430, /&&3%4=083&&000. %22/2 $52).' 0!'%/54.
56. &,53(: : #(!.'%3 4/ 0!'% -!9 "% ,/34!


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

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.