netbsd boot error: panic: MSan: Uninitialized Kmem Memory In strcmp() At Offset 0, From bufinit()

5 views
Skip to first unread message

syzbot

unread,
Dec 6, 2019, 7:15:09 PM12/6/19
to syzkaller-...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 027d7896 cast to proper type
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=10aa542ae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=9544af77043190a5
dashboard link: https://syzkaller.appspot.com/bug?extid=63fae1091f7e25074122
compiler: clang version 3.8.0-2ubuntu4 (tags/RELEASE_380/final)

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+63fae1...@syzkaller.appspotmail.com

[ 1.0000000] panic: MSan: Uninitialized Kmem Memory In strcmp() At Offset
0, From bufinit()

[ 1.0000000] cpu0: Begin traceback...
[ 1.0000000] vpanic() at netbsd:vpanic+0x190 sys/kern/subr_prf.c:336
[ 1.0000000] snprintf() at netbsd:snprintf
[ 1.0000000] kmsan_report_hook.isra.3() at
netbsd:kmsan_report_hook.isra.3+0x149
[ 1.0000000] kmsan_strcmp() at netbsd:kmsan_strcmp+0x1c6
kmsan_shadow_check sys/kern/subr_msan.c:357 [inline]
[ 1.0000000] kmsan_strcmp() at netbsd:kmsan_strcmp+0x1c6
sys/kern/subr_msan.c:733
[ 1.0000000] pool_init() at netbsd:pool_init+0x531
sys/kern/subr_pool.c:945
[ 1.0000000] bufinit() at netbsd:bufinit+0x15f sys/kern/vfs_bio.c:529
[ 1.0000000] main() at netbsd:main+0x11e sys/kern/init_main.c:370
[ 1.0000000] cpu0: End traceback...
[ 1.0000000] fatal breakpoint trap in supervisor mode
[ 1.0000000] trap type 1 code 0 rip 0xffffffff8021e9fd cs 0x8 rflags
0x202 cr2 0 ilevel 0x8 rsp 0xffffffff81e16b90
[ 1.0000000] curlwp 0xffffffff81a5be00 pid 0.1 lowest kstack
0xffffffff81e0f2c0
Stopped in pid 0.1 (system) at netbsd:breakpoint+0x5: 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.

syzbot

unread,
Feb 15, 2020, 9:11:09 AM2/15/20
to syzkaller-...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages