From: "H. Peter Anvin" <hpa@zytor.com>
To: Fengguang Wu <fengguang.wu@intel.com>, kvm <kvm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [qemu64,+smep,+smap] Kernel panic - not syncing: No working init found.
Date: Thu, 13 Feb 2014 07:51:46 -0800 [thread overview]
Message-ID: <52FCEA12.9000006@zytor.com> (raw)
In-Reply-To: <52FCDCE5.4010301@zytor.com>
On 02/13/2014 06:55 AM, H. Peter Anvin wrote:
> On 02/13/2014 04:45 AM, Fengguang Wu wrote:
>> Greetings,
>>
>> I find that when running
>>
>> qemu-system-x86_64 -cpu qemu64,+smep,+smap
>>
>> Some kernels will 100% produce this error, where the error code
>> -13,-14 are -EACCES and -EFAULT:
>>
>> Any ideas?
>>
>
> I notice this is a non-SMAP kernel:
>
> # CONFIG_X86_SMAP is not set
>
> If the kernel turns on SMAP in CR4 even though SMAP isn't enabled in the
> kernel, that is a kernel bug. If Qemu enforces SMAP even if it is
> turned off in CR4, that would be a Qemu bug. I have reproduced the
> failure locally and an am considering both possibilities now.
>
No, it is simply a second kernel bug. I have patches for both and will
push them momentarily.
-hpa
next prev parent reply other threads:[~2014-02-13 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 12:45 [qemu64,+smep,+smap] Kernel panic - not syncing: No working init found Fengguang Wu
2014-02-13 14:55 ` H. Peter Anvin
2014-02-13 15:39 ` H. Peter Anvin
2014-02-13 15:51 ` H. Peter Anvin [this message]
2014-02-13 15:54 ` [tip:x86/urgent] x86, smap: Don' t enable SMAP if CONFIG_X86_SMAP is disabled tip-bot for H. Peter Anvin
2014-02-13 15:54 ` [tip:x86/urgent] x86, smap: smap_violation() is bogus if CONFIG_X86_SMAP is off tip-bot for H. Peter Anvin
2014-02-13 16:18 ` tip-bot for H. Peter Anvin
2014-02-13 16:54 ` tip-bot for H. Peter Anvin
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=52FCEA12.9000006@zytor.com \
--to=hpa@zytor.com \
--cc=fengguang.wu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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.