panic: ffs_valloc: dup alloc (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 93c57cabe698 Implement busdma(9) bounce buffering for raw ..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1439eff8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=efa7100779751865800a

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c3099dfdaeab/disk-93c57cab.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/57ab1b63fbe2/bsd-93c57cab.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8ad2d31f3d11/kernel-93c57cab.xz

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

panic: ffs_valloc: dup alloc
Starting stack trace...
panic(ffffffff834090a9) at panic+0x1ba sys/kern/subr_prf.c:229
ffs_inode_alloc(fffffd806e42f6c8,2000,fffffd807f7d7618,ffff80002a87f550) at ffs_inode_alloc+0x96c sys/ufs/ffs/ffs_alloc.c:404
ufs_makeinode(2000,fffffd80600602e8,ffff80002a87f770,ffff80002a87f7a0) at ufs_makeinode+0xcb sys/ufs/ufs/ufs_vnops.c:1732
ufs_mknod(ffff80002a87f610) at ufs_mknod+0x5b sys/ufs/ufs/ufs_vnops.c:167
VOP_MKNOD(fffffd80600602e8,ffff80002a87f770,ffff80002a87f7a0,ffff80002a87f6a0) at VOP_MKNOD+0x102 sys/kern/vfs_vops.c:121
domknodat(ffff80003c944a68,ffffff9c,400000000000,2000,2e00) at domknodat+0x47e sys/kern/vfs_syscalls.c:1638
syscall(ffff80002a87f940) at syscall+0x97e sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xf77dc5a980, count: 249
End of stack 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 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

[syzbot]

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