panic: mutex 0xffffWAfRd8N0I7NeG:b7 8S8PL1 NUM noNtO T heLOlWd EiREnD m tOxN SY_SlCeaALL v7e5 NUM

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e432ca3c48ac try to simplify the locking code around busy ..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=16d5e0a7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=dd76d5358978ceda9bd2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2cd4b0c96082/disk-e432ca3c.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/a48cad20fda4/bsd-e432ca3c.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f9797235839e/kernel-e432ca3c.xz

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

panic: mutex 0xffffWAfRd8N0I7NeG:b7 8S8PL1 8 noNtO T heLOlWd EiREnD m tOxN SY_SlCeaALL v7e5 5
36S8t7a09r1t2i ngE XIsTta c0k at
racStopped at savectx+0xae: movl $0,%gs:0x680
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*500123 27258 0 0 0x4000000 1 syz-executor
savectx() at savectx+0xae
end of kernel
end trace frame: 0x4913e54270, count: 14
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports. Insufficient info makes it difficult to find and fix bugs.


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