From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: KVM: Do not inject a 64bit fault for a 32bit guest
Date: Thu, 27 Aug 2015 15:45:49 +0100 [thread overview]
Message-ID: <20150827144549.GF21084@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1440684348-5292-1-git-send-email-marc.zyngier@arm.com>
On Thu, Aug 27, 2015 at 03:05:47PM +0100, Marc Zyngier wrote:
> When injecting a fault into a 32bit guest, it seems rather idiotic
> to also inject a 64bit fault that is only going to corrupt the
> guest state, and lead to a situation where we restore an illegal
> context.
>
> Just fix the stupid bug that has been there from day 1.
>
> Cc: stable at vger.kernel.org
> Reported-by: Russell King <linux@arm.linux.org.uk>
s/linux/rmk+kernel/ please
Tested-by: Russell King <rmk+kernel@arm.linux.org.uk>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> ---
> Will: Paolo being on holiday, do you mind merging this one
> via your tree?
I don't think the commit message does this bug justice. The implication
is it's just a guest issue. It isn't, the bug appears to take out the
host kernel in a truely spectacular way.
http://www.arm.linux.org.uk/developer/build/result.php?type=boot&idx=4871
Tested here, the fix stops the host kernel exploding. The crashed kvm
instance can be stopped and a proper kernel can then be booted in a new
guest instance.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2015-08-27 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 14:05 [PATCH] arm64: KVM: Do not inject a 64bit fault for a 32bit guest Marc Zyngier
2015-08-27 14:45 ` Russell King - ARM Linux [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=20150827144549.GF21084@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).