Hello,
syzbot found the following crash on:
HEAD commit: 582fab2b Remove trailing whitespace.
git tree: netbsd
console output:
https://syzkaller.appspot.com/x/log.txt?x=1662a1eae00000
kernel config:
https://syzkaller.appspot.com/x/.config?x=824b23e1f4b6c76b
dashboard link:
https://syzkaller.appspot.com/bug?extid=dc24b61bcad7523fd784
compiler: g++ (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609
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+dc24b6...@syzkaller.appspotmail.com
[ 1.6156896] panic: LO0KaEBUGs Mut0 tarror:2 iun 0: <G528le, PnrsoctentDd
[[ 1.6116886]]k,pu1:disg fitedceb
[ 1.615[ 6].6661.36] sd0: fabricating a geometry
[ 1.6661536] sd0: 8192 MB, 8192 cyl, 64 head, 32 sec, 512 bytes/sect x
16777216 sectors
[ 1.6756192] sd0: fabricating a geometry
[ 1.6756192] vpanic() at sd0: async, 8-bit transfers, tagged queueing
[ 1.6862257] netbsd:vpanic+0x2aa
[ 1.7058806] snprintf() at netbsd:snprintf
[ 1.7260324] lockdebug_abort1() at netbsd:lockdebug_abort1+0x16e
sys/kern/subr_lockdebug.c:799
[ 1.7562684] lockdebug_barrier() at netbsd:lockdebug_barrier+0x157
sys/kern/subr_lockdebug.c:673
[ 1.7663675] mi_switch() at netbsd:mi_switch+0xbf
sys/kern/kern_synch.c:532
[ 1.7663675] idle_loop() at netbsd:idle_loop+0x4bf x86_curlwp
sys/arch/amd64/compile/obj/GENERIC_SYZKALLER/./machine/cpu.h:79 [inline]
[ 1.7663675] idle_loop() at netbsd:idle_loop+0x4bf sys/kern/kern_idle.c:99
[ 1.7663675] cpu_hatch() at netbsd:cpu_hatch+0x3ac
sys/arch/x86/x86/cpu.c:980
[ 1.7663675] md_root_setconf() at netbsd:md_root_setconf
[ 1.7663675] cpu1: End traceback...
[ 1.7663675] fatal breakpoint trap in supervisor mode
[ 1.7663675] trap type 1 code 0 rip 0xffffffff8021dd9d cs 0x8 rflags
0x282 cr2 0 ilevel 0x8 rsp 0xffff8780a57c6d30
[ 1.7663675] curlwp 0xffffcc3647e58100 pid 0.20 lowest kstack
0xffff8780a57c32c0
Stopped in pid 0.20 (system) at netbsd:breakpoint+0x5: leave
db{1}>
---
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.