From: Thomas Huth <thuth@redhat.com>
To: Mohammed Gamal <mgamal@redhat.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, ehabkost@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] intel_iommu: Return error on machines with no PCI
Date: Thu, 14 Sep 2017 22:26:31 +0200 [thread overview]
Message-ID: <4e386f8e-a4f5-7646-a37c-353d6f8068c8@redhat.com> (raw)
In-Reply-To: <1505420247-23685-1-git-send-email-mgamal@redhat.com>
On 14.09.2017 22:17, Mohammed Gamal wrote:
> Starting the following command line causes a segfault
> qemu-system-x86_64 -S -machine isapc,accel=kvm -device intel-iommu
>
> This is due to the fact that the machine type 'isapc' doesn't have
> a PCI bus, while intel_iommu doesn't check if the machine has PCI support
> and subsequently does a null-pointer access. Intel 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/intel_iommu.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c
> index 3a5bb0b..fab0b4b 100644
> --- a/hw/i386/intel_iommu.c
> +++ b/hw/i386/intel_iommu.c
> @@ -3041,6 +3041,13 @@ static void vtd_realize(DeviceState *dev, Error **errp)
> }
>
> bus = pcms->bus;
> +
> + if (!bus) {
> + error_setg(errp, "Machine-type '%s' does not support PCI",
> + mc->name);
> + return;
> + }
> +
> x86_iommu->type = TYPE_INTEL;
>
> if (!vtd_decide_config(s, errp)) {
>
Patch looks basically fine to me, too, but I think I'd also rather
change the "if (!pcms)" at the beginning of the function into "if (!pcms
|| !pcms->bus)" here to use the same error message for both cases.
Thomas
prev parent reply other threads:[~2017-09-14 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 20:17 [Qemu-devel] [PATCH] intel_iommu: Return error on machines with no PCI Mohammed Gamal
2017-09-14 20:26 ` Thomas Huth [this message]
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=4e386f8e-a4f5-7646-a37c-353d6f8068c8@redhat.com \
--to=thuth@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mgamal@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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).