panic: assertwaitok: non-zero mutex count: NUM (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c5a62f9c39e8 drm/amd/display: fix type mismatch in Calcula..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=14997398580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=6cac839a17bc8be499d7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1c1f8807913a/disk-c5a62f9c.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/e84923dddef9/bsd-c5a62f9c.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e24495eeea3e/kernel-c5a62f9c.xz

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

panic: assertwaitok: non-zero mutex count: 2
Starting stack trace...
panic(ffffffff83350409) at panic+0x1ba sys/kern/subr_prf.c:229
assertwaitok() at assertwaitok+0x16f sys/kern/subr_xxx.c:163
mi_switch() at mi_switch+0x2b6 sys/kern/sched_bsd.c:412
yield() at yield+0x61 sys/kern/sched_bsd.c:320
pool_get(ffffffff8393d8c0,1) at pool_get+0x204 sys/kern/subr_pool.c:593
m_copym(fffffd806a253a00,0,3,1) at m_copym+0x1f5 m_get sys/kern/uipc_mbuf.c:-1 [inline]
m_copym(fffffd806a253a00,0,3,1) at m_copym+0x1f5 sys/kern/uipc_mbuf.c:653
somove(ffff8000015b2018,1) at somove+0xae2 sys/kern/uipc_socket.c:1695
sosplice(ffff8000015b2018,0,3,fffffd806e6cc430) at sosplice+0x88d sys/kern/uipc_socket.c:1431
sys_setsockopt(ffff80003a52e2c0,ffff80003ca3d0f0,ffff80003ca3d040) at sys_setsockopt+0x2b9 sys/kern/uipc_syscalls.c:1221
syscall(ffff80003ca3d0f0) at syscall+0x97e mi_syscall sys/sys/syscall_mi.h:-1 [inline]
syscall(ffff80003ca3d0f0) at syscall+0x97e sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xd3ea8e9eeb0, count: 246
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