uvm_fault: vio_rxeof (2)

0 views
Skip to first unread message

syzbot

unread,
May 24, 2024, 7:18:28 AMMay 24
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6859a790d2a4 Inform user land when vltime / pltime changes.
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=111dd8fc980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=1c035fd37d8bf6d359a1

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e032a101680a/disk-6859a790.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/2d4ce5d0ce5d/bsd-6859a790.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0390010e3aed/kernel-6859a790.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1c035f...@syzkaller.appspotmail.com

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.


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages