SYZFAIL: SIGSEGV (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5aa51b7bb462 Instead of assuming the PF gave us 4 queue pa..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=13171a12580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=464d339e42bc02a7c0d0

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/69128aab3d0e/disk-5aa51b7b.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/d3e95beb8714/bsd-5aa51b7b.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/97b8d3686d63/kernel-5aa51b7b.xz

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

SYZFAIL: SIGSEGV
pc-offset:0x247f5854f81 pc:0xdeadbeef addr:0x0 code=1 (errno 35: Resource temporarily unavailable)
syz-executor(42539) in calloc(): recursive call


OpenBSD/amd64 (Amnesiac) (tty00)

login: set $lines = 0
Password:
Login incorrect
login: show panic
Password:
Login incorrect
login: show registers
Password:
Login incorrect
login: uvn_flush: obj=0xfffffd807e75faa8, offset=0x3ff000. error during pageout.
uvn_flush: WARNING: changes to page may be lost!
Abort trap (core dumped)
ps
Password:
Login incorrect
show malloc
login: Password:
Login incorrect
machine ddbcpu 0
login: Password:
Login incorrect
machine ddbcpu 1
login: Password:
Login incorrect
login:


---
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