From: Julia Suvorova <jusual@redhat.com>
To: qemu-devel@nongnu.org
Cc: Igor Mammedov <imammedo@redhat.com>,
Julia Suvorova <jusual@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [PATCH v2] hw/pci/pci: Fix slot check for plugged devices
Date: Tue, 6 Oct 2020 14:59:08 +0200 [thread overview]
Message-ID: <20201006125908.598388-1-jusual@redhat.com> (raw)
If devfn is assigned automatically, 'else' clauses will never be
executed. And if it does not matter for the reserved and available
devfn, because we have already checked it, the check for function0
needs to be done again.
Steps to reproduce:
1. Run QEMU with:
-M q35 \
-device pcie-root-port,id=rp,.. \
-device pci-device,bus=rp
2. Add a new device to the same port:
device_add pci-device,bus=rp
The last command will add the device to slot 1 instead of
failing with "PCI: slot 0 function 0 already occupied..."
Signed-off-by: Julia Suvorova <jusual@redhat.com>
---
v2:
* add example to the commit message [Michael]
hw/pci/pci.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/hw/pci/pci.c b/hw/pci/pci.c
index de0fae10ab..ae132b0b52 100644
--- a/hw/pci/pci.c
+++ b/hw/pci/pci.c
@@ -1034,8 +1034,9 @@ static PCIDevice *do_pci_register_device(PCIDevice *pci_dev,
PCI_SLOT(devfn), PCI_FUNC(devfn), name,
bus->devices[devfn]->name);
return NULL;
- } else if (dev->hotplugged &&
- pci_get_function_0(pci_dev)) {
+ };
+
+ if (dev->hotplugged && pci_get_function_0(pci_dev)) {
error_setg(errp, "PCI: slot %d function 0 already ocuppied by %s,"
" new func %s cannot be exposed to guest.",
PCI_SLOT(pci_get_function_0(pci_dev)->devfn),
--
2.25.4
next reply other threads:[~2020-10-06 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 12:59 Julia Suvorova [this message]
2020-10-07 7:39 ` [PATCH v2] hw/pci/pci: Fix slot check for plugged devices Stefano Garzarella
2020-10-07 10:38 ` Julia Suvorova
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=20201006125908.598388-1-jusual@redhat.com \
--to=jusual@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@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).