syzbot
panic: sx lock still held
Status:
closed as dup on 2021/09/07 22:12
Reported-by: syzbot+a2f195d236221e51c4dc@syzkaller.appspotmail.com
First crash: 2696d, last: 2012d
Sample crash report:
login: panic: sx lock still held
cpuid = 0
time = 1559599259
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame 0xfffffe0020e9a750
vpanic() at vpanic+0x1e0/frame 0xfffffe0020e9a7b0
panic() at panic+0x43/frame 0xfffffe0020e9a810
sx_destroy() at sx_destroy+0x5e/frame 0xfffffe0020e9a830
solisten_proto() at solisten_proto+0xde/frame 0xfffffe0020e9a890
sctp_listen() at sctp_listen+0x4eb/frame 0xfffffe0020e9a900
solisten() at solisten+0x7a/frame 0xfffffe0020e9a940
kern_listen() at kern_listen+0x132/frame 0xfffffe0020e9a980
amd64_syscall() at amd64_syscall+0x436/frame 0xfffffe0020e9aab0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe0020e9aab0
--- syscall (0, FreeBSD ELF64, nosys), rip = 0x45c70a, rsp = 0x7fffdffbbf78, rbp = 0x6bb3b8 ---
KDB: enter: panic
[ thread pid 769 tid 100108 ]
Stopped at kdb_enter+0x6a: movq $0,kdb_why
* Struck through repros no longer work on HEAD.