panic: uvm_faultWAuRnNINe:lSoPck NOT LOdWEREs nN SYSCALL NUM NUM EXIT NUM c

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c0485cf4f019 Slightly improve error reporting in two respe..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=161e719e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=fb8839eeed0d9771aaab

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3578308a7167/disk-c0485cf4.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/651c82fa3be9/bsd-c0485cf4.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f0be395f58a6/kernel-c0485cf4.xz

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

login: panic: uvm_faultWAuRnNINe:lSoPck NOT LOdWEREs nN SYSCALL 91 20 EXIT 0 c
Stopped at savectx+0xae: movl $0,%gs:0x688
TID PID UID PRFLAGS PFLAGS CPU COMMAND
241601 1821 0 0 0x4000000 0 syz-executor
* 29533 30962 0 0x10000002 0 1 syz-executor
savectx() at savectx+0xae
end of kernel
end trace frame: 0x7d6e708a1480, 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