Hello,
syzbot found the following crash on:
HEAD commit: 17de466e loadfile sets errno, return the correct error, no..
git tree: netbsd
console output:
https://syzkaller.appspot.com/x/log.txt?x=14b3fbf2e00000
kernel config:
https://syzkaller.appspot.com/x/.config?x=6e4d6bd2b8e377a2
dashboard link:
https://syzkaller.appspot.com/bug?extid=fa677e9f50dde93c939f
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+fa677e...@syzkaller.appspotmail.com
[ 1.8529666] panic: targEB G:lMut0: <rrogle,iPeriiche5tD: kpin> ock hfid
[ 11.8529666] cpu1[ 1.8529666] : Begin traceback...
[ 1.9130721] sd0: fabricating a geometry
[ 1.9130721] sd0: 8192 MB, 8192 cyl, 64 head, 32 sec, 512 bytes/sect x
16777216 sectors
[ 1.9338980] sd0: fabricating a geometry
[ 1.9457274] vpanic() at netbsd:vpanic+0x241 sys/kern/subr_prf.c:336
[ 1.9631621] sd0: async, 8-bit transfers, tagged queueing
[ 2.0032589] snprintf() at netbsd:snprintf
[ 2.0032589] lockdebug_more() at netbsd:lockdebug_more
[ 2.0032589] lockdebug_barrier() at netbsd:lockdebug_barrier+0xfe
sys/kern/subr_lockdebug.c:684
[ 2.0032589] mi_switch() at netbsd:mi_switch+0xfb
sys/kern/kern_synch.c:532
[ 2.0032589] idle_loop() at netbsd:idle_loop+0x34a x86_curlwp
sys/arch/amd64/compile/obj/GENERIC_SYZKALLER/./machine/cpu.h:79 [inline]
[ 2.0032589] idle_loop() at netbsd:idle_loop+0x34a sys/kern/kern_idle.c:99
[ 2.0032589] cpu_hatch() at netbsd:cpu_hatch+0x267
sys/arch/x86/x86/cpu.c:970
[ 2.0032589] Bad frame pointer: 0xffffdf000f738100
[ 2.0032589] cpu1: End traceback...
[ 2.0032589] fatal breakpoint trap in supervisor mode
[ 2.0032589] trap type 1 code 0 rip 0xffffffff8021ccc5 cs 0x8 rflags
0x246 cr2 0 ilevel 0x8 rsp 0xffffdf016db37b50
[ 2.0032589] curlwp 0xffffdf000f738100 pid 0.20 lowest kstack
0xffffdf016db302c0
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.