panic: uvm_fault_unwire_locked: addrepasnsi cno:t i n k er n e l dmaipagnostic assertion "!_kernel_lock_held()" fa

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 08e9b19a4d03 Use a dynamically-allocated line buffer and r..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=11033e56680000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=9316f1adda47a3ca189f

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f1c70ebe22af/disk-08e9b19a.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/c32273258b13/bsd-08e9b19a.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2a7b0779b758/kernel-08e9b19a.xz

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

panic: uvm_fault_unwire_locked: addrepasnsi cno:t i n k er n e l dmaipagnostic assertion "!_kernel_lock_held()" failed: file "/syzkaller/managers/multicore/kernel/sys/kern/kern_fork.c", line 679
Starting stack trace...
panic(ffffffff8279f1c4) at panic+0x16f sys/kern/subr_prf.c:229
__assert(ffffffff8281f847,ffffffff82803e0d,2a7,ffffffff827d8622) at __assert+0x29 sys/kern/subr_prf.c:157
proc_trampoline_mp() at proc_trampoline_mp+0x135
end trace frame: 0x0, count: 254
End of stack trace.

dump to dev 4,1 not possible
rpeabnooiticn:g k.e.r.n
el diagnostiSeaBIOS (version 1.8.2-google)
Total RAM Size = 0x0000000080000000 = 2048 MiB
CPUs found: 2 Max CPUs supported: 2
SeaBIOS (version 1.8.2-google)
Machine UUID f8e08a03-81bc-3227-53c0-939594373760
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=4194304 = 2048 MiB
drive 0x000f28a0: PCHS=0/0/0 translation=lba LCHS=520/128/63 s=4194304
Sending Seabios boot VM event.
Booting from Hard Disk 0...
>> OpenBSD/amd64 BOOT 3.65
boot> set $lines = 0
set: syntax error
boot> set $maxwidth = 0
set: syntax error
boot> show panic
boot: illegal argument panic
boot> trace
boot> show registers
boot> show proc
boot> ps
boot> show all locks
boot> show malloc
boot> show all pools
boot> machine ddbcpu 0
machine: syntax error
boot> trace
boot> machine ddbcpu 1
machine: syntax error
boot> trace


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.