syzbot


uvm_fault: pool_gc_pages

Status: auto-obsoleted due to no activity on 2023/01/17 22:31
Reported-by: syzbot+107fd5a7aaa9867553b0@syzkaller.appspotmail.com
First crash: 297d, last: 110d

Sample crash report:
uvm_fault(0xffffffff82ac6c60, 0x0, 0, 2) -> e
kernel: page fault trap, code=0
Stopped at      pool_gc_pages+0x1a5:    movq    %rax,0(%rcx)
    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
*109369  55223      0     0x14000      0x200    0  systqmp
pool_gc_pages(0) at pool_gc_pages+0x1a5 pool_p_remove sys/kern/subr_pool.c:1049 [inline]
pool_gc_pages(0) at pool_gc_pages+0x1a5 sys/kern/subr_pool.c:1576
taskq_thread(ffffffff829882c0) at taskq_thread+0x9b sys/kern/kern_task.c:449
end trace frame: 0x0, count: 13
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 (4):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci-openbsd-main 2022/10/19 22:31 openbsd 5a8d990a1c03 b31320fc .config console log report [disk image] [bsd.gdb] [kernel image] uvm_fault: pool_gc_pages
ci-openbsd-main 2022/08/17 16:03 openbsd 8e8e1d336104 4e72d229 .config console log report uvm_fault: pool_gc_pages
ci-openbsd-main 2022/06/26 04:29 openbsd b86449360131 a371c43c .config console log report uvm_fault: pool_gc_pages
ci-openbsd-main 2022/04/15 19:41 openbsd f0263d44f958 8bcc32a6 .config console log report uvm_fault: pool_gc_pages
* Struck through repros no longer work on HEAD.