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

[syzbot <syzbot+687cb7d90fcd55ac5a89%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=17391183980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=739e57438eb9ed9e
dashboard link: https://syzkaller.appspot.com/bug?extid=687cb7d90fcd55ac5a89
compiler:       Debian clang version 15.0.6

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a4b7439c9b9c/disk-03662591.raw.xz
netbsd.gdb: https://storage.googleapis.com/syzbot-assets/372be152029a/netbsd-03662591.gdb.xz

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

[   7.3004515] panic: kernel debugging assertion "rw_lock_held(&map->lock)" failed: file "/syzkaller/managers/ci2-netbsd-kmsan/kernel/sys/uvm/uvm_map.c", line 1703 
[   7.3112337] cpu0: Begin traceback...
[   7.3304570] vpanic() at netbsd:vpanic+0xc9d
[   7.3704438] kern_assert() at netbsd:kern_assert+0x228
[   7.4204409] uvm_map_lookup_entry() at netbsd:uvm_map_lookup_entry+0x291
[   7.4704437] uvm_unmap_remove() at netbsd:uvm_unmap_remove+0x82e sys/uvm/uvm_map.c:2333
[   7.5204398] uvmspace_free() at netbsd:uvmspace_free+0x39a sys/uvm/uvm_map.c:4425
[   7.5704400] exit1() at netbsd:exit1+0xe1e sys/kern/kern_exit.c:349
[   7.6204409] sys_exit() at netbsd:sys_exit+0x1d6
[   7.6704605] syscall() at netbsd:syscall+0x576 sy_invoke sys/sys/syscallvar.h:94 [inline]
[   7.6704605] syscall() at netbsd:syscall+0x576 sys/arch/x86/x86/syscall.c:137
[   7.6804384] --- syscall (number 1) ---
[   7.7004388] netbsd:syscall+0x576:
[   7.7004388] cpu0: End traceback...
[   7.7004388] fatal breakpoint trap in supervisor mode
[   7.7004388] trap type 1 code 0 rip 0xffffffff80236885 cs 0x8 rflags 0x282 cr2 0xfffffc00c77ed000 ilevel 0 rsp 0xfffffc00c7801730
[   7.7004388] curlwp 0xfffffc00123106c0 pid 200.200 lowest kstack 0xfffffc00c77fa2c0
Stopped in pid 200.200 (sysctl) at      netbsd:breakpoint+0x5:  leave
breakpoint() at netbsd:breakpoint+0x5
vpanic() at netbsd:vpanic+0xc9d
kern_assert() at netbsd:kern_assert+0x228
uvm_map_lookup_entry() at netbsd:uvm_map_lookup_entry+0x291
uvm_unmap_remove() at netbsd:uvm_unmap_remove+0x82e sys/uvm/uvm_map.c:2333
uvmspace_free() at netbsd:uvmspace_free+0x39a sys/uvm/uvm_map.c:4425
exit1() at netbsd:exit1+0xe1e sys/kern/kern_exit.c:349
sys_exit() at netbsd:sys_exit+0x1d6
syscall() at netbsd:syscall+0x576 sy_invoke sys/sys/syscallvar.h:94 [inline]
syscall() at netbsd:syscall+0x576 sys/arch/x86/x86/syscall.c:137
--- syscall (number 1) ---
netbsd:syscall+0x576:
ds          8918
es          6473
fs          1720
gs          0
rdi         5
rsi         0
rbp         fffffc00c7801730
rbx         0
rdx         1
rcx         fffffc00123106c0
rax         fffffc0012378918
--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/0000000000005536d0061f9a9d2b%40google.com.