From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P . Berrange" <berrange@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Anthony Perard" <anthony.perard@citrix.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: [RFC PATCH-for-5.1? v3 0/2] hw/isa: Allow 8/16/32 bit access on ISA bus after CVE-2020-13754 fix
Date: Tue, 21 Jul 2020 14:31:52 +0200 [thread overview]
Message-ID: <20200721123154.5302-1-f4bug@amsat.org> (raw)
Surgical attempt to fix the issue, as we are in freeze...
If such kludge is tolerable, it must be reverted first thing
after release.
Fixes:
- https://lore.kernel.org/xen-devel/20200630170913.123646-1-anthony.perard@citrix.com/T/
- https://bugs.debian.org/964793
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964247
- https://bugs.launchpad.net/bugs/1886318
Philippe Mathieu-Daudé (2):
memory: Allow monkey-patching MemoryRegion access sizes
hw/isa/isa-bus: Ensure ISA I/O regions are 8/16/32-bit accessible
include/exec/memory.h | 7 ++++++-
hw/isa/isa-bus.c | 14 ++++++++++++++
softmmu/memory.c | 12 ++++++++----
3 files changed, 28 insertions(+), 5 deletions(-)
--
2.21.3
next reply other threads:[~2020-07-21 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 12:31 Philippe Mathieu-Daudé [this message]
2020-07-21 12:31 ` [RFC PATCH-for-5.1? v3 1/2] memory: Allow monkey-patching MemoryRegion access sizes Philippe Mathieu-Daudé
2020-07-21 12:33 ` Peter Maydell
2020-07-21 12:39 ` Philippe Mathieu-Daudé
2020-07-21 12:49 ` Peter Maydell
2020-07-21 14:23 ` Philippe Mathieu-Daudé
2020-07-21 14:32 ` Peter Maydell
2020-07-21 12:31 ` [RFC PATCH-for-5.1? v3 2/2] hw/isa/isa-bus: Ensure ISA I/O regions are 8/16/32-bit accessible Philippe Mathieu-Daudé
2020-07-21 12:41 ` Peter Maydell
2020-07-21 12:55 ` Philippe Mathieu-Daudé
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=20200721123154.5302-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=anthony.perard@citrix.com \
--cc=berrange@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).