From: Mohammed Gamal <mgamal@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, ehabkost@redhat.com, mst@redhat.com,
thuth@redhat.com, Mohammed Gamal <mgamal@redhat.com>
Subject: [Qemu-devel] [PATCH] amd_iommu: Return error on machines with no PCI
Date: Thu, 14 Sep 2017 21:50:19 +0200 [thread overview]
Message-ID: <1505418619-16284-1-git-send-email-mgamal@redhat.com> (raw)
Starting the following command line causes a segfault
qemu-system-x86_64 -S -machine isapc,accel=kvm -device amd-iommu
This is due to the fact that the machine type 'isapc' doesn't have
a PCI bus, while amd_iommu doesn't check if the machine has PCI support
and subsequently does a null-pointer access. AMD IOMMU shouldn't even work
if the target machine doesn't have PCI.
Add a check for PCI on the given machine type and return an error if PCI
is not supported.
Signed-off-by: Mohammed Gamal <mgamal@redhat.com>
---
hw/i386/amd_iommu.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/hw/i386/amd_iommu.c b/hw/i386/amd_iommu.c
index 334938a..9a667b7 100644
--- a/hw/i386/amd_iommu.c
+++ b/hw/i386/amd_iommu.c
@@ -1153,6 +1153,13 @@ static void amdvi_realize(DeviceState *dev, Error **err)
}
bus = pcms->bus;
+
+ if (!bus) {
+ error_setg(err, "Machine-type '%s' does not support PCI",
+ mc->name);
+ return;
+ }
+
s->iotlb = g_hash_table_new_full(amdvi_uint64_hash,
amdvi_uint64_equal, g_free, g_free);
--
1.8.3.1
next reply other threads:[~2017-09-14 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 19:50 Mohammed Gamal [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-14 20:18 [Qemu-devel] [PATCH] amd_iommu: Return error on machines with no PCI Mohammed Gamal
2017-09-14 20:24 ` Thomas Huth
2017-09-14 20:31 ` Eduardo Habkost
2017-09-15 2:07 ` Peter Xu
2017-09-15 9:59 ` Mohammed Gamal
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=1505418619-16284-1-git-send-email-mgamal@redhat.com \
--to=mgamal@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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 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).