panic: vop_generic_bado

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9d920c79bf2d Declare membar_datadep_consumer() inline to f..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=14f0e861700000
kernel config: https://syzkaller.appspot.com/x/.config?x=bf87b6915a88cd0d
dashboard link: https://syzkaller.appspot.com/bug?extid=119db8268feba2009062

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+119db8...@syzkaller.appspotmail.com

panic: vop_generic_bado
p
Starting stack trace...
panic(ffffffff8257845c) at panic+0x16b sys/kern/subr_prf.c:233
vop_generic_badop(ffff800021219f48) at vop_generic_badop+0x1b sys/kern/vfs_default.c:133
VOP_STRATEGY(fffffd806741a4d8,fffffd8066a4a268) at VOP_STRATEGY+0x9b sys/kern/vfs_vops.c:644
bwrite(fffffd8066a4a268) at bwrite+0x1f0 sys/kern/vfs_bio.c:763
VOP_BWRITE(fffffd8066a4a268) at VOP_BWRITE+0x4a sys/kern/vfs_vops.c:656
ufs_mkdir(ffff80002121a1e0) at ufs_mkdir+0x6b4 sys/ufs/ufs/ufs_vnops.c:1248
VOP_MKDIR(fffffd806a8b4b00,ffff800021
21a340,ffff80002121a370,ffff80002121a270) at VOP_MKDIR+0xbf sys/kern/vfs_vops.c:404
domkdirat(ffff8000ffff4d20,ffffff9c,7f7fffffaf80,1ff) at domkdirat+0x121 sys/kern/vfs_syscalls.c:3101
syscall(ffff80002121a4f0) at syscall+0x489 mi_syscall sys/sys/syscall_mi.h:102 [inline]
syscall(ffff80002121a4f0) at syscall+0x489 sys/arch/amd64/amd64/trap.c:585
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7f7fffffaff0, count: 247
End of stack trace.
syncing disks...panic: ke2rn3e l di2a gnosti
c assertion "!_kernel_l
ock_held()" failed: fil
e "/syzkaller/managers/
multicore/kernel/sys/uv
m/uvm_map.c", line 2734

Starting stack trace...
panic(ffffffff82581ba1) at panic+0x16b sys/kern/subr_prf.c:233
__assert(ffffffff825f995f,ffffffff82604f98,aae,ffffffff825b73fa) at __assert+0x25 sys/kern/subr_prf.c:161
uvm_map_teardown(fffffd8063349300) at uvm_map_teardow1n +0x2e8
uvmspace_free(fffffd8063349300) at uvmspace_free+0xa6 sys/uvm/uvm_map.c:3685
reaper(ffff8000210f9a40) at reaper+0x18b sys/kern/kern_exit.c:457
end trace frame: 0x0, count: 252
End of stack trace.

dump to dev 4,1 not possible
rpeaboniocti:n 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.

[Anton Lindqvist]

#syz invalid