netbsd test error: panic: kernel debugging assertion "rw_lock_held(&map->lock)" failed: file "/syzkaller/managers/ci2-netbsd-kubsan/kernel/

[syzbot <syzbot+c7c6bbf515944411762d%syzkaller.appspotmail.com@localhost>]

Hello,

syzbot found the following issue on:

HEAD commit:    036625911e3f Redo uvm_map.c 1.414 without the null pointer..
git tree:       netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1577d96b980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1420f906d33d9f1f
dashboard link: https://syzkaller.appspot.com/bug?extid=c7c6bbf515944411762d
compiler:       g++ (Debian 12.2.0-14) 12.2.0

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f2ccb6019671/disk-03662591.raw.xz
netbsd.gdb: https://storage.googleapis.com/syzbot-assets/7d95e7a0d41a/netbsd-03662591.gdb.xz

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

[   6.8932636] panic: kernel debugging assertion "rw_lock_held(&map->lock)" failed: file "/syzkaller/managers/ci2-netbsd-kubsan/kernel/sys/uvm/uvm_map.c", line 1703 
[   6.8932636] cpu0: Begin traceback...
[   6.9032572] vpanic() at netbsd:vpanic+0x2f3 sys/kern/subr_prf.c:288
[   6.9432670] kern_assert() at netbsd:kern_assert+0x63 sys/arch/amd64/amd64/db_disasm.c:1074
[   6.9732615] uvm_map_lookup_entry() at netbsd:uvm_map_lookup_entry+0x2fb sys/uvm/uvm_map.c:1703
[   7.0032699] uvm_unmap_remove() at netbsd:uvm_unmap_remove+0xec sys/uvm/uvm_map.c:2333
[   7.0332581] uvmspace_free() at netbsd:uvmspace_free+0x2a9 sys/uvm/uvm_map.c:4425
[   7.0532581] uvm_proc_exit() at netbsd:uvm_proc_exit+0xe7 sys/uvm/uvm_glue.c:444
[   7.0832579] exit1() at netbsd:exit1+0x4ec sys/kern/kern_exit.c:349
[   7.1132585] sys_exit() at netbsd:sys_exit+0xd4 sys/kern/kern_exit.c:181
[   7.1632600] syscall() at netbsd:syscall+0x35d sy_call sys/sys/syscallvar.h:65 [inline]
[   7.1632600] syscall() at netbsd:syscall+0x35d sy_invoke sys/sys/syscallvar.h:94 [inline]
[   7.1632600] syscall() at netbsd:syscall+0x35d sys/arch/x86/x86/syscall.c:137
[   7.1732590] --- syscall (number 1) ---
[   7.1932595] netbsd:syscall+0x35d:
[   7.1932595] cpu0: End traceback...
[   7.1932595] fatal breakpoint trap in supervisor mode
[   7.1932595] trap type 1 code 0 rip 0xffffffff8023547d cs 0x8 rflags 0x286 cr2 0xffffdb0247fec000 ilevel 0 rsp 0xffffdb0248042c50
[   7.1932595] curlwp 0xffff801452bbc6c0 pid 200.200 lowest kstack 0xffffdb024803e2c0
Stopped in pid 200.200 (sysctl) at      netbsd:breakpoint+0x5:  leave
breakpoint() at netbsd:breakpoint+0x5
db_panic() at netbsd:db_panic+0xec sys/ddb/db_panic.c:71
vpanic() at netbsd:vpanic+0x2f3 sys/kern/subr_prf.c:288
kern_assert() at netbsd:kern_assert+0x63 sys/arch/amd64/amd64/db_disasm.c:1074
uvm_map_lookup_entry() at netbsd:uvm_map_lookup_entry+0x2fb sys/uvm/uvm_map.c:1703
uvm_unmap_remove() at netbsd:uvm_unmap_remove+0xec sys/uvm/uvm_map.c:2333
uvmspace_free() at netbsd:uvmspace_free+0x2a9 sys/uvm/uvm_map.c:4425
uvm_proc_exit() at netbsd:uvm_proc_exit+0xe7 sys/uvm/uvm_glue.c:444
exit1() at netbsd:exit1+0x4ec sys/kern/kern_exit.c:349
sys_exit() at netbsd:sys_exit+0xd4 sys/kern/kern_exit.c:181
syscall() at netbsd:syscall+0x35d sy_call sys/sys/syscallvar.h:65 [inline]
syscall() at netbsd:syscall+0x35d sy_invoke sys/sys/syscallvar.h:94 [inline]
syscall() at netbsd:syscall+0x35d sys/arch/x86/x86/syscall.c:137
--- syscall (number 1) ---
netbsd:syscall+0x35d:
ds          f3ea
es          2c10
fs          2c60
gs          10
rdi         5
rsi         0
rbp         ffffdb0248042c50
rbx         1
rdx         ffff801452bbcab8
--db_more--

---
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 syzkaller%googlegroups.com@localhost.

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

-- 
You received this message because you are subscribed to the Google Groups "syzkaller-netbsd-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-netbsd-bugs+unsubscribe%googlegroups.com@localhost.
To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-netbsd-bugs/0000000000002cf4ce061f9a32b9%40google.com.