From: Anthony PERARD <firstname.lastname@example.org>
To: "Roger Pau Monné" <email@example.com>
Ian Jackson <firstname.lastname@example.org>, Wei Liu <email@example.com>,
Jan Beulich <firstname.lastname@example.org>,
Andrew Cooper <email@example.com>
Subject: Re: [XEN PATCH] hvmloader: Fix reading ACPI PM1 CNT value
Date: Wed, 1 Jul 2020 10:10:31 +0100 [thread overview]
Message-ID: <20200701091031.GC2030@perard.uk.xensource.com> (raw)
On Wed, Jul 01, 2020 at 09:52:57AM +0200, Roger Pau Monné wrote:
> On Tue, Jun 30, 2020 at 06:09:13PM +0100, Anthony PERARD wrote:
> > In order to get the CNT value from QEMU, we were supposed to read a
> > word, according to the implementation in QEMU. But it has been lax and
> > allowed to read a single byte. This has changed with commit
> > 5d971f9e6725 ("memory: Revert "memory: accept mismatching sizes in
> > memory_region_access_valid"") and result in hvmloader crashing on
> > the BUG_ON.
> This is a bug on the QEMU side, the ACPI spec states: "Accesses to PM1
> control registers are accessed through byte and word accesses.".
> That's on section 220.127.116.11.1 PM1 Control Registers of my copy of the
> ACPI spec (6.2A).
I guess we can ignore this patch then, and I should write a patch for
> I'm fine with this if such bogus behavior has made it's way into a
> release version of QEMU, but it needs to state it's a workaround for a
> QEMU bug, not a bug in hvmloader.
It hasn't, but might.
> IMO the QEMU change should be reverted.
The change can't be reverted, it is to fix a CVE and isn't related to
ACPI. But we can fix the emulator.
> Thanks, Roger.
prev parent reply other threads:[~2020-07-01 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 17:09 [XEN PATCH] hvmloader: Fix reading ACPI PM1 CNT value Anthony PERARD
2020-07-01 7:52 ` Roger Pau Monné
2020-07-01 9:10 ` Anthony PERARD [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).