From: "Michael S. Tsirkin" <mst@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Igor Mammedov" <imammedo@redhat.com>,
"John Snow" <jsnow@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.10-rc4?] acpi: pcihp: fix use-after-free for machines previous pc-1.7 compat
Date: Wed, 23 Aug 2017 16:17:30 +0300 [thread overview]
Message-ID: <20170823161718-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <887ee497-5518-f6bc-56ec-2c2626cdf1f2@redhat.com>
On Wed, Aug 23, 2017 at 07:40:39AM +0200, Thomas Huth wrote:
> On 23.08.2017 02:10, Philippe Mathieu-Daudé wrote:
> > On 08/22/2017 07:42 PM, Michael S. Tsirkin wrote:
> >> On Tue, Aug 22, 2017 at 06:43:43PM -0300, Philippe Mathieu-Daudé wrote:
> >>> 9e047b982452 "piix4: add acpi pci hotplug support" introduced a new
> >>> property
> >>> 'use_acpi_pci_hotplug' for pc-1.7 and older machines.
> >>> c24d5e0b91d1 "convert ACPI PCI hotplug to use hotplug-handler API"
> >>> added the
> >>> qbus hotplug handlers but forgot to check for the 'use_acpi_pci_hotplug'
> >>> property.
> >>>
> >>> Check for use_acpi_pci_hotplug before calling
> >>> acpi_pcihp_device_[un]plug_cb().
> [...]
> >>> Reported-by: Thomas Huth <thuth@redhat.com>
> >>> Message-Id: <59a56959-ca12-ea75-33fa-ff07eba1b090@redhat.com>
> >>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> >>
> >> Looks like this is a very old bug, isn't it?
> >> Objections to merging this after the release?
> >
> > Yes, I'm also inclined to delay it so we can release 2.10, I tagged
> > "2.10-rc4" since Thomas sent it as a bug within the 2.10 window so I'll
> > let him decide if it is worth crying wolf :) It's very likely no-one but
> > him used pre-pc-i440fx-1.7 the last 3 years, not even thinking about hot
> > plugging AHCI devices :D
>
> I'm fine if this gets included in 2.11 - it's quite unlikely that a user
> tries hot-plug ahci on such an old machine type, I think. But we maybe
> should include this in the 2.10.1 stable release, so I'm putting
> qemu-stable on CC now.
>
> Anyway, your patch seems to fix the issue for me, thanks!
>
> Tested-by: Thomas Huth <thuth@redhat.com>
ok, pls remember to repost or ping after the release.
next prev parent reply other threads:[~2017-08-23 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 21:43 [Qemu-devel] [PATCH for-2.10-rc4?] acpi: pcihp: fix use-after-free for machines previous pc-1.7 compat Philippe Mathieu-Daudé
2017-08-22 22:42 ` Michael S. Tsirkin
2017-08-23 0:10 ` Philippe Mathieu-Daudé
2017-08-23 5:40 ` Thomas Huth
2017-08-23 6:04 ` Thomas Huth
2017-08-23 8:35 ` Igor Mammedov
2017-08-23 13:17 ` Michael S. Tsirkin [this message]
2017-08-23 8:32 ` Igor Mammedov
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=20170823161718-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=f4bug@amsat.org \
--cc=imammedo@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.