linux-next boot error (2)

[syzbot]

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@xxxxxxxxxxxxxxxxxxxxxxxxx

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@xxxxxxxxxxxxxxxxx

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with  
syzbot.