page fault in Xosyscall

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0dc1ecc02249 lint: document suppressed LDBL_MAX warning mo..
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=11832733c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=739e57438eb9ed9e
dashboard link: https://syzkaller.appspot.com/bug?extid=44319bd0eb7194bdb1b4
compiler: Debian clang version 15.0.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b3faf4b28f0c/disk-0dc1ecc0.raw.xz
netbsd.gdb: https://storage.googleapis.com/syzbot-assets/26891b3147cd/netbsd-0dc1ecc0.gdb.xz

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

[ 251.1708310] fatal page faultfatal page fault in supervisor mode
[ 251.1848981] in supervisor mode
[ 251.1848981] trap type 6 code 0 rip 0xffffffff802000d7 cs 0x8 rflags 0x10006 cr2 0x7 ilevel 0 rsp 0xffffe380c7b9cf00
[ 251.1848981] trap type 6 code 0 rip 0xffffffff802000d7 cs 0x8 rflags 0x10006 cr2 0x7 ilevel 0 rsp 0xffffe380d0c3af00
[ 251.1848981] curlwp 0xffffe38013908340 pid 2122.1267 lowest kstack 0xffffe380c7b952c0
k[ er2n51e.l2:1 p0a30g2e 0f]a uflatta tlr appag,e c ofadue=l0t
Stopped in pid 2122.1267 (syz-executor.2) at netbsd:Xosyscall+0xc7: movsb (%rsi),%es:(%rdi)
?
Xosyscall() at netbsd:Xosyscall+0xc7
[ 251.2230928] prevented access to 0x7421a10a1008 (SMAP)
[ 251.2230928] fatal page fault in supervisor mode
[ 251.2230928] trap type 6 code 0x1 rip 0xffffffff818d8de2 cs 0x8 rflags 0x10246 cr2 0x7421a10a1008 ilevel 0x8 rsp 0xffffe380c7b9bbe0
[ 251.2230928] curlwp 0xffffe38013908340 pid 2122.1267 lowest kstack 0xffffe380c7b952c0
kernel: page fault trap, code=0
Faulted in DDB; continuing...


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

[syzbot]

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