panic: ffs_valloc: dup alloc
Starting stack trace...
panic(ffffffff830e812b) at panic+0x1d0 sys/kern/subr_prf.c:229
ffs_inode_alloc(fffffd807e436440,41c0,fffffd807f7d35b0,ffff8000371a9cc8) at ffs_inode_alloc+0x96c sys/ufs/ffs/ffs_alloc.c:404
ufs_mkdir(ffff8000371a9d30) at ufs_mkdir+0x113 sys/ufs/ufs/ufs_vnops.c:1112
VOP_MKDIR(fffffd806ee1ecd8,ffff8000371a9e90,ffff8000371a9ec0,ffff8000371a9dc0) at VOP_MKDIR+0x102 sys/kern/vfs_vops.c:394
domkdirat(ffff8000ffff2020,ffffff9c,74b2bd90f3d0,1c0) at domkdirat+0x179 sys/kern/vfs_syscalls.c:3099
syscall(ffff8000371aa040) at syscall+0xaf8 mi_syscall sys/sys/syscall_mi.h:179 [inline]
syscall(ffff8000371aa040) at syscall+0xaf8 sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x74b2bd90f390, count: 250
End of stack trace.
syncing disks...panic: kernel diagnostic assertion "((flags & PGO_LOCKED) != 0 && rw_lock_held(uobj->vmobjlock)) || (flags & PGO_LOCKED) == 0" failed: file "/syzkaller/managers/multicore/kernel/sys/uvm/uvm_vnode.c", line 955
Starting stack trace...
panic(ffffffff830e8503) at panic+0x1d0 sys/kern/subr_prf.c:229
__assert(ffffffff83099bdf,ffffffff82fd79cb,3bb,ffffffff830b434d) at __assert+0x29
uvn_get(fffffd806cf529d0,73000,ffff8000371de8a0,ffff8000371de71c,3,1,6f6cdbaf922b804f,73000) at uvn_get+0x69b sys/uvm/uvm_vnode.c:954
uvm_fault_lower_lookup(ffff8000371de920,ffff8000371de958,ffff8000371de8a0) at uvm_fault_lower_lookup+0x10e sys/uvm/uvm_fault.c:1128
uvm_fault_lower(ffff8000371de920,ffff8000371de958,ffff8000371de8a0,0) at uvm_fault_lower+0x74 sys/uvm/uvm_fault.c:1227
uvm_fault(fffffd806c4fb6f8,110c2a6000,0,1) at uvm_fault+0x301 sys/uvm/uvm_fault.c:637
upageflttrap(ffff8000371deaa0,110c2a685a) at upageflttrap+0xa9 sys/arch/amd64/amd64/trap.c:188
usertrap(ffff8000371deaa0) at usertrap+0x2d8 sys/arch/amd64/amd64/trap.c:436
recall_trap() at recall_trap+0x8
end of kernel
end trace frame: 0x719eaafff450, count: 248
End of stack trace.

dump to dev 4,1 not possible