panic: mutex 0xffffWAfRd8N0I7NeG:b7 8S8PL1 NUM noNtO T heLOlWd EiREnD m tOxN SY

panic: mutex 0xffffWAfRd8N0I7NeG:b7 8S8PL1 NUM noNtO T heLOlWd EiREnD m tOxN SY_SlCeaALL v7e5 NUM

Status: auto-obsoleted due to no activity on 2025/01/19 11:15
Reported-by: syzbot+dd76d5358978ceda9bd2@syzkaller.appspotmail.com
First crash: 371d, last: 371d

Sample crash report:

panic: mutex 0xffffWAfRd8N0I7NeG:b7 8S8PL1 8 noNtO T heLOlWd EiREnD m tOxN SY_SlCeaALL v7e5 5
36S8t7a09r1t2i ngE XIsTta c0k  at
racStopped at      savectx+0xae:   movl    $0,%gs:0x680
    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
*500123  27258      0           0  0x4000000    1  syz-executor
savectx() at savectx+0xae
end of kernel
end trace frame: 0x4913e54270, count: 14
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports.  Insufficient info makes it difficult to find and fix bugs.

Crashes (1):
Time	Kernel	Commit	Syzkaller	Config	Log	Report	Syz repro	C repro	VM info	Assets (help?)	Manager	Title
2024/10/21 11:14	openbsd	e432ca3c48ac	cd6fc0a3	.config	console log	report					ci-openbsd-multicore	panic: mutex 0xffffWAfRd8N0I7NeG:b7 8S8PL1 NUM noNtO T heLOlWd EiREnD m tOxN SY_SlCeaALL v7e5 NUM

* ~~Struck through~~ repros no longer work on HEAD.