panic: acqupirainincg: b lo c kkaerblneel s l e ep l o c k d i a gwintohs tsipc i nl oc k o r c r it i c a l

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: bf088e2b2bca Extract the type from the ICMP6 header before..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=122c48ed700000
kernel config: https://syzkaller.appspot.com/x/.config?x=bf87b6915a88cd0d
dashboard link: https://syzkaller.appspot.com/bug?extid=4df8f2f3da7bef2b1a30

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

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

panic: acqupirainincg: b lo c kkaerblneel s l e ep l o c k d i a gwintohs tsipc i nl oc k o r c r it i c a l s e ct i o n he ld (k e r n el _l o c k) & k er ne l _ l o c k
aStsasertritniogn s "t!ac_kke trnrealc_el.o..ck
_held()" failed: file "/psyaznkiacl(flefrf/fmafnffagfe8r25sa4/1mu8l4)ti coart e/kernel/sys/uvm/uvpman_imcap+0.cx1"6,b l
ine 2734
Parallel traceback,w itsunpepssre_schseecdk.o.r.
der(ffffffff82a6f1a0,9,0) at witness_checkorder+0x116d sys/kern/subr_witness.c:833
__mp_lock(ffffffff82a6ef98) at __mp_lock+0xa1 read_rflags machine/cpufunc.h:195 [inline]
__mp_lock(ffffffff82a6ef98) at __mp_lock+0xa1 intr_disable machine/cpufunc.h:216 [inline]
__mp_lock(ffffffff82a6ef98) at __mp_lock+0xa1 sys/kern/kern_lock.c:142
selwakeup(fffffd80769b8168) at
sdeulmwapk etuop d+ev0 x146,
1 not possible
sorwakeup(fffffdpraebnoioct:in kg.er..ne
l 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 68bf758f-d7e1-83a6-91e2-c70932eb46bc
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 0x000f2780: 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.53
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.

[Aleksandr Nogikh]

#syz invalid

> --
> You received this message because you are subscribed to the Google Groups "syzkaller-openbsd-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-openbsd...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-openbsd-bugs/00000000000075c73305dadd2f0b%40google.com.