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=14137cdee00000
kernel config:
https://syzkaller.appspot.com/x/.config?x=6e4d6bd2b8e377a2
dashboard link:
https://syzkaller.appspot.com/bug?extid=20a441586671c17e1447
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+20a441...@syzkaller.appspotmail.com
[ 1.8309802] panic: sd0KDE sc: Mute tarror: l_s itc<,oo8l , Pe sictknteis
[[ .88008822] cpu1d sk fi traceba[ 1.8309802] ck...
[ 1.9044779] sd0: fabricating a geometry
[ 1.9044779] sd0: 8192 MB, 8192 cyl, 64 head, 32 sec, 512 bytes/sect x
16777216 sectors
[ 1.9232799] vpanic() at sd0: fabricating a geometry
[ 1.9335679] netbsd:vpanic+0x241
[ 1.9611842] sd0: async, 8-bit transfers, tagged queueing
[ 1.9812050] snprintf() at netbsd:snprintf
[ 2.0413016] lockdebug_more() at netbsd:lockdebug_more
[ 2.0913754] lockdebug_barrier() at netbsd:lockdebug_barrier+0xfe
sys/kern/subr_lockdebug.c:684
[ 2.0913754] mi_switch() at netbsd:mi_switch+0xfb
sys/kern/kern_synch.c:532
[ 2.0913754] idle_loop() at netbsd:idle_loop+0x34a x86_curlwp
sys/arch/amd64/compile/obj/GENERIC_SYZKALLER/./machine/cpu.h:79 [inline]
[ 2.0913754] idle_loop() at netbsd:idle_loop+0x34a sys/kern/kern_idle.c:99
[ 2.0913754] cpu_hatch() at netbsd:cpu_hatch+0x270
sys/arch/x86/x86/cpu.c:980
[ 2.0913754] Bad frame pointer: 0xffffdb000f738100
[ 2.0913754] cpu1: End traceback...
[ 2.0913754] fatal breakpoint trap in supervisor mode
[ 2.0913754] trap type 1 code 0 rip 0xffffffff8021ccb5 cs 0x8 rflags
0x246 cr2 0 ilevel 0x8 rsp 0xffffdb016db37b50
[ 2.0913754] curlwp 0xffffdb000f738100 pid 0.20 lowest kstack
0xffffdb016db302c0
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.