syzbot


panic: thread ADDR cannotW ARexNiIt NGw:h ilSPeL h oNlOTdi nLgO WsElReEepD lOoNck sSY

Status: closed as dup on 2019/02/01 06:52
Reported-by: syzbot+1a5e2edcaeeab34327db@syzkaller.appspotmail.com
First crash: 1904d, last: 1904d
Duplicate of
Title Repro Cause bisect Fix bisect Count Last Reported
witness: thread exiting with locks held syz 679 1697d 1908d

Sample crash report:
login: panic: thread 0xffff800020b939e0 cannotW ARexNiIt NGw:h ilSPeL h oNlOTdi nLgO WsElReEepD lOoNck sSY
SCSALtLo pp95e d1 a4 tEXIT 0 9
      db_enter+0x18:  addq    $0x8,%rsp
    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
 116692  67475     73    0x100010          0    0  syslogd
*156780  12971      0     0x14000      0x200    1  reaper
db_enter() at db_enter+0x18 sys/arch/amd64/amd64/db_interface.c:399
panic() at panic+0x16c sys/kern/subr_prf.c:208
witness_thread_exit(8e2ffed4ec25a572) at witness_thread_exit+0x244 sys/kern/subr_witness.c:1377
reaper(0) at reaper+0x14f sys/kern/kern_exit.c:412
end trace frame: 0x0, count: 11
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
2019/02/01 04:27 openbsd dc36d2c7c3b1 aa432daf .config console log report ci-openbsd-multicore
* Struck through repros no longer work on HEAD.