From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:54706) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gf4OX-000555-OO for qemu-devel@nongnu.org; Thu, 03 Jan 2019 09:54:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gf4OU-0002NT-AF for qemu-devel@nongnu.org; Thu, 03 Jan 2019 09:54:49 -0500 Date: Thu, 3 Jan 2019 15:54:38 +0100 From: Cornelia Huck Message-ID: <20190103155438.68d6afe3.cohuck@redhat.com> In-Reply-To: <20190103140246.50791-1-liq3ea@163.com> References: <20190103140246.50791-1-liq3ea@163.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] s390: avoid potential null dereference in s390_pcihost_unplug() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Li Qiang Cc: walling@linux.ibm.com, rth@twiddle.net, david@redhat.com, pasic@linux.ibm.com, borntraeger@de.ibm.com, qemu-s390x@nongnu.org, qemu-devel@nongnu.org, peter.maydell@linaro.org, Pierre Morel On Thu, 3 Jan 2019 06:02:46 -0800 Li Qiang 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. > > Spotted by Coverity: CID 1398593 > > Signed-off-by: Li Qiang > --- > hw/s390x/s390-pci-bus.c | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c > index 15759b6514..b3122268a3 100644 > --- a/hw/s390x/s390-pci-bus.c > +++ b/hw/s390x/s390-pci-bus.c > @@ -956,6 +956,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 for not supported device" > + " type: %s", object_get_typename(OBJECT(dev))); > + return; I think that is something that really Should Not Happen. However, looking at s390_pcihost_plug, we just do nothing if the plugged device does not match any of the expected three values. Maybe we should also set an error in that case there? > } > > switch (pbdev->state) {