syzbot


panic: uvm_fault_unwire_locked: WARaNdIdNGre:s sS PnotL iNn OmT aLpO

Status: closed as invalid on 2023/10/11 13:32
Reported-by: syzbot+c38f1013a7022f0d0ddd@syzkaller.appspotmail.com
First crash: 211d, last: 211d

Sample crash report:
panic: uvm_fault_unwire_locked: WARaNdIdNGre:s sS PnotL  iNn OmT aLpO
WSEtRaErDt inONg  sSYtaSckCA tLrL a7c3e .5.4.
1065216 EXIT 0 a
Stopped at      savectx+0xae:   movl    $0,%gs:0x558
    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
*240132  42124      0           0  0x4000000    0  syz-executor.7
 174286  42124      0           0  0x4000000    1K syz-executor.7
savectx() at savectx+0xae
end of kernel
end trace frame: 0xec7304a7bd0, 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
2023/10/11 08:53 openbsd b6eb132903d9 83165b57 .config console log report ci-openbsd-multicore panic: uvm_fault_unwire_locked: WARaNdIdNGre:s sS PnotL iNn OmT aLpO
* Struck through repros no longer work on HEAD.