witness: userret: mlockall

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8c9607973553 Remove TABLE_BITS from gcm128.
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=120f9f68580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=0f45b9ae27dbbbc7cf9e

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/10faf15ff3b4/disk-8c960797.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/2a697b0a8269/bsd-8c960797.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b2c97cbfd8ec/kernel-8c960797.xz

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

witness: userret: returning with the following locks held:
exclusive rwlock vmmaplk r = 0 (0xfffffd806ebda6a8)
#0 witness_lock+0x5bb stacktrace_save sys/sys/stacktrace.h:37 [inline]
#0 witness_lock+0x5bb sys/kern/subr_witness.c:1160
#1 rw_do_enter_write+0x3ea sys/kern/kern_rwlock.c:316
#2 vm_map_lock_ln+0x12e sys/uvm/uvm_map.c:5227
#3 uvm_map_pageable_wire+0x588 sys/uvm/uvm_map.c:2128
#4 sys_mlockall+0x85 sys/uvm/uvm_mmap.c:914
#5 syscall+0xb08 mi_syscall sys/sys/syscall_mi.h:176 [inline]
#5 syscall+0xb08 sys/arch/amd64/amd64/trap.c:579
#6 Xsyscall+0x128
panic: witness_warn
Starting stack trace...
panic(ffffffff83382cc8) at panic+0x1d0 sys/kern/subr_prf.c:229
witness_warn(2,0,ffffffff83341f50) at witness_warn+0x850 witness_debugger sys/kern/subr_witness.c:2576 [inline]
witness_warn(2,0,ffffffff83341f50) at witness_warn+0x850 sys/kern/subr_witness.c:1485
userret(ffff80003b7fc028) at userret+0x3a4 sys/kern/kern_sig.c:2227
syscall(ffff8000383e8330) at syscall+0x9c0 mi_syscall_return sys/sys/syscall_mi.h:203 [inline]
syscall(ffff8000383e8330) at syscall+0x9c0 sys/arch/amd64/amd64/trap.c:600
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x92bdbfa1240, count: 252
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

[syzbot]

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