witness: thread exiting with locks held (2)

Status: closed as dup on 2022/07/02 06:37
Reported-by: syzbot+07b70cc7acb6ddff7134@syzkaller.appspotmail.com
First crash: 1527d, last: 1526d
▶ ▼ Duplicate of
Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported
witness: userret: sendmsg -1 syz, C 28 1526d 1527d
▶ ▼ Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
openbsd witness: thread exiting with locks held (3) -1 3 456d 457d 3/4 fixed on 2025/06/07 10:16
openbsd witness: thread exiting with locks held -1 syz 679 2567d 2777d 0/4 closed as dup on 2019/02/21 21:47

Sample crash report:
witness: thread 0xffff800027bf8fc0 exiting with the following locks held:
exclusive rwlock solock r = 0 (0xfffffd8077391df8)
#0  witness_lock+0x44d
#1  unp_solock_peer+0xa6 sys/kern/uipc_usrreq.c:163
#2  uipc_usrreq+0x7c6 sys/kern/uipc_usrreq.c:350
#3  sosend+0x61b sys/kern/uipc_socket.c:657
#4  sendit+0x65d sys/kern/uipc_syscalls.c:682
#5  sys_sendmsg+0x198 sys/kern/uipc_syscalls.c:589
#6  syscall+0x4c3 mi_syscall sys/sys/syscall_mi.h:101 [inline]
#6  syscall+0x4c3 sys/arch/amd64/amd64/trap.c:585
#7  Xsyscall+0x128
panic: thread 0xffff800027bf8fc0 cannot exit while holding sleeplocks

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/07/02 10:57 openbsd a4a82b864d54 1434eec0 .config console log report ci-openbsd-multicore witness: thread exiting with locks held
2022/07/02 04:09 openbsd a4a82b864d54 1434eec0 .config console log report ci-openbsd-multicore witness: thread exiting with locks held
* Struck through repros no longer work on HEAD.