syzbot


uvm_fault: vio_rxeof (2)

Status: upstream: reported on 2024/05/24 11:18
Reported-by: syzbot+1c035fd37d8bf6d359a1@syzkaller.appspotmail.com
First crash: 28d, last: 28d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
openbsd uvm_fault: vio_rxeof syz 15700 1427d 1738d 3/3 fixed on 2020/08/05 06:16

Sample crash report:
uvm_fault(0xfffffd806fbf91b8, 0xa, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at      vio_rxeof+0x196:        movzwl  0xa(%rbx),%r12d
    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
*464129  71298      0   0x8000000          0    0  syz-executor.1
 295967  34962  60928   0x8000010          0    1  syz-executor.3
vio_rxeof(ffff8000001a0000) at vio_rxeof+0x196 sys/dev/pv/if_vio.c:1120
vio_rx_intr(ffff8000001a0050) at vio_rx_intr+0x48 sys/dev/pv/if_vio.c:1160
intr_handler(ffff80002a2bd1b0,ffff80000067b200) at intr_handler+0x93 sys/arch/amd64/amd64/intr.c:543
Xintr_ioapic_edge25_untramp() at Xintr_ioapic_edge25_untramp+0x18f
end of kernel
end trace frame: 0x711f3d112ae0, 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
2024/05/24 11:17 openbsd 6859a790d2a4 8f98448e .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore uvm_fault: vio_rxeof
* Struck through repros no longer work on HEAD.