netbsd boot error: panic: rw_vector_enter,292: uninitialized lock (lock=ADDR, from=ADDR)

0 views
Skip to first unread message

syzbot

unread,
Oct 29, 2019, 2:53:07 PM10/29/19
to syzkaller-...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: a7218e01 Regen.
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=11daae1f600000
kernel config: https://syzkaller.appspot.com/x/.config?x=824b23e1f4b6c76b
dashboard link: https://syzkaller.appspot.com/bug?extid=3603976e92b9843b5b44

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

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

[ 1.0000000] panic: rw_vector_enter,292: uninitialized lock
(lock=0xffffffff85ddbc08, from=ffffffff81d1458a)
[ 1.0000000] cpu0: Begin traceback...
[ 1.0000000] Skipping crash dump on recursive panic
[ 1.0000000] panic: UBSan: Undefined Behavior in
/syzkaller/managers/netbsd-kubsan/kernel/sys/arch/x86/x86/db_memrw.c:105:20,
load of misaligned address 0xffffffff81ed1456 for type 'int' which requires
4 byte alignment

[ 1.0000000] Faulted in mid-traceback; aborting...
[ 1.0000000] fatal breakpoint trap in supervisor mode
[ 1.0000000] trap type 1 code 0 rip 0xffffffff8021dddd cs 0x8 rflags
0x202 cr2 0x2c ilevel 0x8 rsp 0xffffffff86038800
[ 1.0000000] curlwp 0xffffffff8508c000 pid 0.1 lowest kstack
0xffffffff860352c0
Stopped in pid 0.1 (system) at ffffffff8021dddd: leave
db{0}>


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

Maxime Villard

unread,
Dec 1, 2019, 3:08:40 AM12/1/19
to syzbot, syzkaller-...@googlegroups.com
was a one-off

#syz invalid
Reply all
Reply to author
Forward
0 new messages