From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Ignore pci unplug requests for unpluggable devices (CVE-2011-1751)
Date: Thu, 19 May 2011 13:12:58 +0200 [thread overview]
Message-ID: <4DD4FB3A.1060600@redhat.com> (raw)
In-Reply-To: <m3zkmj80yh.fsf@blackfin.pond.sub.org>
Hi,
>> diff --git a/hw/acpi_piix4.c b/hw/acpi_piix4.c
>> index 96f5222..6c908ff 100644
>> --- a/hw/acpi_piix4.c
>> +++ b/hw/acpi_piix4.c
>> @@ -471,11 +471,13 @@ static void pciej_write(void *opaque, uint32_t addr, uint32_t val)
>> BusState *bus = opaque;
>> DeviceState *qdev, *next;
>> PCIDevice *dev;
>> + PCIDeviceInfo *info;
>> int slot = ffs(val) - 1;
>>
>> QLIST_FOREACH_SAFE(qdev,&bus->children, sibling, next) {
>> dev = DO_UPCAST(PCIDevice, qdev, qdev);
>> - if (PCI_SLOT(dev->devfn) == slot) {
>> + info = container_of(qdev->info, PCIDeviceInfo, qdev);
>> + if (PCI_SLOT(dev->devfn) == slot&& !info->no_hotplug) {
>> qdev_free(qdev);
>> }
>> }
>
> Looks good, but what about pcie_cap_slot_hotplug()?
Dunno, didn't look at q35 yet. I'd expect the root bus isn't
hot-pluggable, so the guest wouldn't be able to rip out any essential
chipset devices. But having someone more familier with pcie + q35
double-check would be good ...
cheers,
Gerd
next prev parent reply other threads:[~2011-05-19 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 9:13 [Qemu-devel] [PULL] Fix CVE-2011-1751 Gerd Hoffmann
2011-05-19 9:13 ` [Qemu-devel] [PATCH] Ignore pci unplug requests for unpluggable devices (CVE-2011-1751) Gerd Hoffmann
2011-05-19 10:00 ` Markus Armbruster
2011-05-19 11:12 ` Gerd Hoffmann [this message]
2011-05-19 11:23 ` Markus Armbruster
2011-05-19 11:52 ` Isaku Yamahata
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=4DD4FB3A.1060600@redhat.com \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.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).