All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ani Sinha <ani@anisinha.ca>
Cc: Igor Mammedov <imammedo@redhat.com>,
	Julia Suvorova <jusual@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] Fix a gap where acpi_pcihp_find_hotplug_bus() returns a non-hotpluggable bus
Date: Thu, 3 Sep 2020 06:16:08 -0400	[thread overview]
Message-ID: <20200903061515-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAARzgwwFRUOoq7GOttzJVT8+67+7uNugC529SB8DX242p8A_QQ@mail.gmail.com>

On Thu, Sep 03, 2020 at 03:41:13PM +0530, Ani Sinha wrote:
> On Sep 3, 2020, 15:35 +0530, Michael S. Tsirkin <mst@redhat.com>, wrote:
> 
>     On Sat, Aug 29, 2020 at 01:42:33PM +0530, Ani Sinha wrote:
> 
>         When ACPI hotplug for the root bus is disabled, the bsel property for
>         that
> 
>         bus is not set. Please see the following commit:
> 
> 
> 
>         3d7e78aa7777f ("Introduce a new flag for i440fx to disable PCI hotplug
>         on the root bus").
> 
> 
> 
>         As a result, when acpi_pcihp_find_hotplug_bus() is called
> 
>         with bsel set to 0, it may return the root bus. This would be wrong
>         since the
> 
>         root bus is not hotpluggable. In general, this can potentially happen
>         to other
> 
>         buses as well.
> 
>         In this patch, we fix the issue in this function by checking if the bus
>         returned
> 
>         by the function is actually hotpluggable. If not, we simply return
>         NULL. This
> 
>         avoids the scenario where we are actually returning a non-hotpluggable
>         bus.
> 
> 
> 
>         Signed-off-by: Ani Sinha <ani@anisinha.ca>
> 
> 
> 
>     What exactly are the consequences though?
> 
> 
> The root bus might get ejected by the user when it should not if the user does
> the following:
> 
> outl 0xae10 0
> outl 0xae08 your_slot
> 
> Please see Julia’s comment:
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg734548.html

OK so patch looks good, but please add all this in the commit log.

-- 
MST



  parent reply	other threads:[~2020-09-03 10:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29  8:12 [PATCH] Fix a gap where acpi_pcihp_find_hotplug_bus() returns a non-hotpluggable bus Ani Sinha
2020-09-02  7:30 ` Ani Sinha
2020-09-03 10:04 ` Michael S. Tsirkin
2020-09-03 10:11   ` Ani Sinha
2020-09-03 10:12     ` Ani Sinha
2020-09-03 10:16     ` Michael S. Tsirkin [this message]
2020-09-03 10:26       ` Ani Sinha

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=20200903061515-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=ani@anisinha.ca \
    --cc=imammedo@redhat.com \
    --cc=jusual@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 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.