From: syzbot <syzbot+762a577f56cfb1574647@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, alexander.levin@verizon.com,
dhowells@redhat.com, linux-kernel@vger.kernel.org,
linux@dominikbrodowski.net, luc.vanoostenryck@gmail.com,
nikolaus.voss@loewensteinmedical.de, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com
Subject: linux-next boot error (2)
Date: Thu, 06 Sep 2018 01:21:03 -0700 [thread overview]
Message-ID: <0000000000006082bd05752f92bb@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 509d1f0c294a Add linux-next specific files for 20180906
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=157b857a400000
kernel config: https://syzkaller.appspot.com/x/.config?x=d1a648893bbc933
dashboard link: https://syzkaller.appspot.com/bug?extid=762a577f56cfb1574647
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
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+762a577f56cfb1574647@syzkaller.appspotmail.com
kernel panic: VFS: Unable to mount root fs on unknown-block(8,1) driver: sd
0801 2096128 sda1 24d8ab2f-01
1f00 128 mtdblock0
(driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(8,1)
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.19.0-rc2-next-20180906+ #60
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113
panic+0x238/0x4e7 kernel/panic.c:184
mount_block_root+0x61f/0x71f init/do_mounts.c:442
mount_root+0x2d0/0x317 init/do_mounts.c:562
prepare_namespace+0x26c/0x2ab init/do_mounts.c:621
kernel_init_freeable+0x590/0x5ae init/main.c:1163
kernel_init+0x11/0x1b3 init/main.c:1063
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:415
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
next reply other threads:[~2018-09-06 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 8:21 syzbot [this message]
2018-09-06 8:41 ` linux-next boot error (2) David Howells
2018-09-06 8:52 ` Dmitry Vyukov
2018-09-11 20:16 ` David Howells
2018-09-11 20:34 ` Stephen Rothwell
2018-09-11 21:24 ` David Howells
2018-11-21 13:32 ` Dmitry Vyukov
2018-11-27 10:25 ` David Howells
2018-11-27 10:38 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000006082bd05752f92bb@google.com \
--to=syzbot+762a577f56cfb1574647@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@verizon.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=luc.vanoostenryck@gmail.com \
--cc=nikolaus.voss@loewensteinmedical.de \
--cc=sfr@canb.auug.org.au \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.