From: Halil Pasic <pasic@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Li Qiang <liq3ea@163.com>,
peter.maydell@linaro.org, walling@linux.ibm.com,
david@redhat.com, qemu-devel@nongnu.org, borntraeger@de.ibm.com,
qemu-s390x@nongnu.org, rth@twiddle.net
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH v2] s390: avoid potential null dereference in s390_pcihost_unplug()
Date: Fri, 4 Jan 2019 16:05:15 +0100 [thread overview]
Message-ID: <20190104160515.1b4a6dc1@oc2783563651> (raw)
In-Reply-To: <20190104151005.42b6f111.cohuck@redhat.com>
On Fri, 4 Jan 2019 15:10:05 +0100
Cornelia Huck <cohuck@redhat.com> wrote:
> On Thu, 3 Jan 2019 07:16:12 -0800
> Li Qiang <liq3ea@163.com> wrote:
>
> > When getting the 'pbdev', the if...else has no default branch.
> > From Coverity, the 'pbdev' maybe null when the 'dev' is not
> > the TYPE_PCI_BRIDGE/TYPE_PCI_DEVICE/TYPE_S390_PCI_DEVICE.
> > This patch adds a default branch for device plug and unplug.
> >
> > Spotted by Coverity: CID 1398593
> >
> > Signed-off-by: Li Qiang <liq3ea@163.com>
> > ---
> > Adds a default branch for device plug per Cornelia's review.
> >
> > hw/s390x/s390-pci-bus.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
> > index 15759b6514..fe48a36ff6 100644
> > --- a/hw/s390x/s390-pci-bus.c
> > +++ b/hw/s390x/s390-pci-bus.c
> > @@ -912,6 +912,9 @@ static void s390_pcihost_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
> > pbdev->fh = pbdev->idx;
> > QTAILQ_INSERT_TAIL(&s->zpci_devs, pbdev, link);
> > g_hash_table_insert(s->zpci_table, &pbdev->idx, pbdev);
> > + } else {
> > + error_setg(errp, "s390: device plug request for not supported device"
> > + " type: %s", object_get_typename(OBJECT(dev)));
>
> Maybe make this "s390/pci: plugging device type <%s> is not supported"?
>
Under what circumstances could/does this happen? I mean how can this
be triggered by the user?
Regards,
Halil
> > }
> > }
> >
> > @@ -956,6 +959,10 @@ static void s390_pcihost_unplug(HotplugHandler *hotplug_dev, DeviceState *dev,
> > } else if (object_dynamic_cast(OBJECT(dev), TYPE_S390_PCI_DEVICE)) {
> > pbdev = S390_PCI_DEVICE(dev);
> > pci_dev = pbdev->pdev;
> > + } else {
> > + error_setg(errp, "s390: device unplug request for not supported device"
> > + " type: %s", object_get_typename(OBJECT(dev)));
>
> Halil has a point when he suggests an assert here. If we fence the
> device type in the plug function, I can't think of a way we would end
> up here.
>
> > + return;
> > }
> >
> > switch (pbdev->state) {
>
>
next prev parent reply other threads:[~2019-01-04 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 15:16 [Qemu-devel] [PATCH v2] s390: avoid potential null dereference in s390_pcihost_unplug() Li Qiang
2019-01-04 14:10 ` Cornelia Huck
2019-01-04 14:33 ` [Qemu-devel] 答复: [PATCH v2] s390: avoid potential null dereference ins390_pcihost_unplug() Li Qiang
2019-01-07 9:02 ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2019-01-07 15:48 ` [Qemu-devel] " Cornelia Huck
2019-01-07 15:54 ` Peter Maydell
2019-01-07 15:57 ` Cornelia Huck
2019-01-07 16:04 ` Peter Maydell
2019-01-07 16:10 ` Cornelia Huck
2019-01-08 6:42 ` 李强
2019-01-04 15:05 ` Halil Pasic [this message]
2019-01-07 15:45 ` [Qemu-devel] [qemu-s390x] [PATCH v2] s390: avoid potential null dereference in s390_pcihost_unplug() Cornelia Huck
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=20190104160515.1b4a6dc1@oc2783563651 \
--to=pasic@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=liq3ea@163.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=walling@linux.ibm.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).