panic: vopp_ganenier:ic_ a

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 176eada02fb4 Add flag SDEV_UFI so umass_scsi_attach() can ..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=137762da280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=37aae2007af5f3d50b77

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/805d959be662/disk-176eada0.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/05a6ce3113a1/bsd-176eada0.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8cf564573c81/kernel-176eada0.xz

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

panic: vopp_ganenier:ic_ a
kernel diagnostic assertion "!_kernel_lock_held()" failed: file "/syzkaller/managers/multicore/kernel/sys/kern/kern_fork.c", line 675
Starting stack trace...
panic(ffffffff8278d96b) at panic+0x16f sys/kern/subr_prf.c:229
__assert(ffffffff8280fdbe,ffffffff827f27c7,2a3,ffffffff827c73f5) 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


---
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 change 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.