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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a66c1d641baa Revert previous. Let's deal with it when the ..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=133f41e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=5b4a2a90d1e5ea8e82e0

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ec28922e8db3/disk-a66c1d64.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/014bb09e67d7/bsd-a66c1d64.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/98c827ccb984/kernel-a66c1d64.xz

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

SYZFAIL: tun: can't open device
device=/dev/tap1 (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/tap1 (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/tap1 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap1 (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/tap1 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap1 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap1 (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/tap1 (errno 16: Device busy)
ifconfig: socket: No buffer space available
SYZFAIL: tun: can't open device
device=/dev/tap1 (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/tap1 (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/tap1 (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/tap1 (errno 16: Device busy)
SYZFAIL: ioctl remote attach failed
(errno 16: Device busy)
SYZFAIL: repeatedly failed to execute the program
proc=1 req=2 state=1 status=67 (errno 35: Resource temporarily unavailable)
56. &,53(: /"*=08&&&&&$8071"!03%0, /&&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