From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751914AbaBMOzr (ORCPT ); Thu, 13 Feb 2014 09:55:47 -0500 Received: from terminus.zytor.com ([198.137.202.10]:38414 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751818AbaBMOzq (ORCPT ); Thu, 13 Feb 2014 09:55:46 -0500 Message-ID: <52FCDCE5.4010301@zytor.com> Date: Thu, 13 Feb 2014 06:55:33 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Fengguang Wu , kvm CC: LKML , Ingo Molnar , Thomas Gleixner Subject: Re: [qemu64,+smep,+smap] Kernel panic - not syncing: No working init found. References: <20140213124550.GA30497@localhost> In-Reply-To: <20140213124550.GA30497@localhost> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. -hpa