syzbot

 sign-in | mailing list | source | docs
🐞 Open [115]
🐞 Fixed [291]
🐞 Invalid [890]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

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

Status: auto-closed as invalid on 2021/10/22 18:00
Reported-by: syzbot+9bac12f8eb6f5fb51be1@syzkaller.appspotmail.com
First crash: 1497d, last: 1497d
▶ ▼ Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
openbsd SYZFAIL: tun: can't open device (6) -1 31 28d 69d 0/3 upstream: reported on 2025/06/22 13:40
openbsd SYZFAIL: tun: can't open device (3) -1 86 1324d 1324d 0/3 closed as invalid on 2022/01/15 08:41
openbsd SYZFAIL: tun: can't open device (5) -1 82 175d 190d 0/3 auto-obsoleted due to no activity on 2025/04/27 11:29
openbsd SYZFAIL: tun: can't open device -1 syz 4 1640d 1640d 3/3 fixed on 2021/03/10 05:59
openbsd SYZFAIL: tun: can't open device (4) -1 8 313d 415d 0/3 auto-obsoleted due to no activity on 2025/01/18 18:59

Sample crash report:
SYZFAIL: tun: can't open device
device=/dev/tap1 (errno 16: Device busy)


OpenBSD/amd64 (ci-openbsd-multicore-0.c.syzkaller.internal) (tty00)

login:

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2021/07/24 17:59 openbsd e9c3085b033d 4d1b57d4 .config console log report ci-openbsd-multicore SYZFAIL: tun: can't open device
* Struck through repros no longer work on HEAD.