From: Paul Moore <pmoore@redhat.com>
To: Huang Ying <ying.huang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [fs] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
Date: Wed, 21 Jan 2015 09:29:27 -0500 [thread overview]
Message-ID: <2014590.Q7f0SpfhCT@sifl> (raw)
In-Reply-To: <1421825538.6126.28.camel@intel.com>
On Wednesday, January 21, 2015 03:32:18 PM Huang Ying wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 5dc5218840e1268de639150a851978bb19c341df ("fs: create proper filename
> objects using getname_kernel()")
>
> [ 16.813397] 010f 65536 ram15 (driver?)
> [ 16.815041] fc00 268435456 vda driver: virtio_blk
> [ 16.816777] fc10 268435456 vdb driver: virtio_blk
> [ 16.818544] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(1,0) [ 16.819520] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> 3.19.0-rc5-next-20150120-g5d0eebb #799 [ 16.819520] Hardware name: QEMU
> Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140531_083030-gandalf
> 04/01/2014 [ 16.819520] ffff8800076a0000 ffff880006f47db8
> ffffffff81b7a16b ffffffff810cf061 [ 16.819520] ffffffff81fd6ce5
> ffff880006f47e38 ffffffff81b749fd ffffffff822459b0 [ 16.819520]
> ffff880000000010 ffff880006f47e48 ffff880006f47de8 ffff003500626476 [
> 16.819520] Call Trace:
> [ 16.819520] [<ffffffff81b7a16b>] dump_stack+0x4c/0x65
> [ 16.819520] [<ffffffff810cf061>] ? console_unlock+0x398/0x3c7
> [ 16.819520] [<ffffffff81b749fd>] panic+0xc9/0x1f7
> [ 16.819520] [<ffffffff824e84aa>] mount_block_root+0x201/0x218
> [ 16.819520] [<ffffffff824e871f>] mount_root+0x13f/0x14a
> [ 16.819520] [<ffffffff824e92fc>] ? initrd_load+0x2d7/0x2e6
> [ 16.819520] [<ffffffff824e8897>] prepare_namespace+0x16d/0x1a6
> [ 16.819520] [<ffffffff824e815a>] kernel_init_freeable+0x268/0x278
> [ 16.819520] [<ffffffff81b6bb61>] ? rest_init+0xca/0xca
> [ 16.819520] [<ffffffff81b6bb6f>] kernel_init+0xe/0xda
> [ 16.819520] [<ffffffff81b881fc>] ret_from_fork+0x7c/0xb0
> [ 16.819520] [<ffffffff81b6bb61>] ? rest_init+0xca/0xca
> [ 16.819520] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range:
> 0xffffffff80000000-0xffffffff9fffffff)
Thanks for reporting the problem, we're currently working on a fix:
* https://lkml.org/lkml/2015/1/20/710
--
paul moore
security @ redhat
prev parent reply other threads:[~2015-01-21 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 7:32 [LKP] [fs] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) Huang Ying
2015-01-21 14:29 ` Paul Moore [this message]
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=2014590.Q7f0SpfhCT@sifl \
--to=pmoore@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox