syzbot


panic: uvmW_AfaRuNlItNG_:unwi rSPeL_ loNOckTe Ld:OW EaRdEdDr eOsNs SnYoStC AiLn mLa p7

Status: upstream: reported on 2025/09/18 11:54
Reported-by: syzbot+d5ac99fce469b593eab2@syzkaller.appspotmail.com
First crash: 1d10h, last: 1d10h

Sample crash report:
panic: uvmW_AfaRuNlItNG_:unwi rSPeL_ loNOckTe Ld:OW EaRdEdDr eOsNs  SnYoStC AiLn mLa p7
3 57S3tart44i ngE XsItTack  0t raa
ceStopped at      savectx+0xae:   movl    $0,%gs:0x688
    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
 443046  51968      0           0  0x4000000    0K syz-executor
*155150  51968      0           0  0x4000000    1  syz-executor
savectx() at savectx+0xae
end of kernel
end trace frame: 0xf58e10a9e90, 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
2025/09/18 11:53 openbsd 6d22a4a7112d e2beed91 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: uvmW_AfaRuNlItNG_:unwi rSPeL_ loNOckTe Ld:OW EaRdEdDr eOsNs SnYoStC AiLn mLa p7
* Struck through repros no longer work on HEAD.