From: Pankaj Gupta <pagupta@redhat.com> To: mst@redhat.com Cc: pagupta@redhat.com, peter.maydell@linaro.org, cohuck@redhat.com, qemu-devel@nongnu.org, david@redhat.com Subject: [Qemu-devel] [PATCH 2/3] virtio pmem: remove memdev null check Date: Fri, 12 Jul 2019 13:05:53 +0530 [thread overview] Message-ID: <20190712073554.21918-3-pagupta@redhat.com> (raw) In-Reply-To: <20190712073554.21918-1-pagupta@redhat.com> Coverity reports that when we're assigning vi->size we handle the "pmem->memdev is NULL" case; but we then pass it into object_get_canonical_path(), which unconditionally dereferences it and will crash if it is NULL. If this pointer can be NULL then we need to do something else here. We are removing 'pmem->memdev' null check here as memdev will never be null in this function. Signed-off-by: Pankaj Gupta <pagupta@redhat.com> --- hw/virtio/virtio-pmem.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hw/virtio/virtio-pmem.c b/hw/virtio/virtio-pmem.c index adbfb603ab..17c196d107 100644 --- a/hw/virtio/virtio-pmem.c +++ b/hw/virtio/virtio-pmem.c @@ -134,8 +134,8 @@ static void virtio_pmem_fill_device_info(const VirtIOPMEM *pmem, VirtioPMEMDeviceInfo *vi) { vi->memaddr = pmem->start; - vi->size = pmem->memdev ? memory_region_size(&pmem->memdev->mr) : 0; - vi->memdev = object_get_canonical_path(OBJECT(pmem->memdev)); + vi->size = memory_region_size(&pmem->memdev->mr); + vi->memdev = object_get_canonical_path(OBJECT(pmem->memdev)); } static MemoryRegion *virtio_pmem_get_memory_region(VirtIOPMEM *pmem, -- 2.14.5
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com> To: qemu-devel@nongnu.org Cc: Peter Maydell <peter.maydell@linaro.org>, Cornelia Huck <cohuck@redhat.com>, Pankaj Gupta <pagupta@redhat.com> Subject: [Qemu-devel] [PULL 7/8] virtio pmem: remove memdev null check Date: Fri, 12 Jul 2019 11:36:41 -0400 [thread overview] Message-ID: <20190712073554.21918-3-pagupta@redhat.com> (raw) Message-ID: <20190712153641.zoK6kep8gjSxeILA76zpXVCVQpB9RsW13z630PKoMPs@z> (raw) In-Reply-To: <20190712153504.14937-1-mst@redhat.com> From: Pankaj Gupta <pagupta@redhat.com> Coverity reports that when we're assigning vi->size we handle the "pmem->memdev is NULL" case; but we then pass it into object_get_canonical_path(), which unconditionally dereferences it and will crash if it is NULL. If this pointer can be NULL then we need to do something else here. We are removing 'pmem->memdev' null check here as memdev will never be null in this function. Signed-off-by: Pankaj Gupta <pagupta@redhat.com> Message-Id: <20190712073554.21918-3-pagupta@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Reviewed-by: Cornelia Huck <cohuck@redhat.com> --- hw/virtio/virtio-pmem.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hw/virtio/virtio-pmem.c b/hw/virtio/virtio-pmem.c index adbfb603ab..17c196d107 100644 --- a/hw/virtio/virtio-pmem.c +++ b/hw/virtio/virtio-pmem.c @@ -134,8 +134,8 @@ static void virtio_pmem_fill_device_info(const VirtIOPMEM *pmem, VirtioPMEMDeviceInfo *vi) { vi->memaddr = pmem->start; - vi->size = pmem->memdev ? memory_region_size(&pmem->memdev->mr) : 0; - vi->memdev = object_get_canonical_path(OBJECT(pmem->memdev)); + vi->size = memory_region_size(&pmem->memdev->mr); + vi->memdev = object_get_canonical_path(OBJECT(pmem->memdev)); } static MemoryRegion *virtio_pmem_get_memory_region(VirtIOPMEM *pmem, -- MST
next prev parent reply other threads:[~2019-07-12 7:36 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-12 7:35 [Qemu-devel] [PATCH 0/3] virtio pmem: coverity fixes Pankaj Gupta 2019-07-12 7:35 ` [Qemu-devel] [PATCH 1/3] virtio pmem: fix wrong mem region condition Pankaj Gupta 2019-07-12 8:50 ` Stefano Garzarella 2019-07-12 9:56 ` Cornelia Huck 2019-07-12 15:36 ` [Qemu-devel] [PULL 6/8] " Michael S. Tsirkin 2019-07-12 17:05 ` [Qemu-devel] [PATCH 1/3] " Philippe Mathieu-Daudé 2019-07-15 6:44 ` David Hildenbrand 2019-07-12 7:35 ` Pankaj Gupta [this message] 2019-07-12 10:01 ` [Qemu-devel] [PATCH 2/3] virtio pmem: remove memdev null check Cornelia Huck 2019-07-12 15:36 ` [Qemu-devel] [PULL 7/8] " Michael S. Tsirkin 2019-07-12 7:35 ` [Qemu-devel] [PATCH 3/3] virtio pmem: remove transational device info Pankaj Gupta 2019-07-12 10:03 ` Cornelia Huck 2019-07-12 10:06 ` Pankaj Gupta 2019-07-12 15:36 ` [Qemu-devel] [PULL 8/8] virtio pmem: remove transitional names Michael S. Tsirkin 2019-07-15 6:44 ` [Qemu-devel] [PATCH 3/3] virtio pmem: remove transational device info David Hildenbrand 2019-07-15 7:22 ` Pankaj Gupta 2019-07-15 7:25 ` David Hildenbrand 2019-07-12 10:03 ` [Qemu-devel] [PATCH 0/3] virtio pmem: coverity fixes Cornelia Huck 2019-07-12 10:05 ` Pankaj Gupta -- strict thread matches above, loose matches on Subject: below -- 2019-07-12 15:36 [Qemu-devel] [PULL 0/8] virtio, pc, pci: fixes, cleanups, tests Michael S. Tsirkin 2019-07-10 14:14 ` [Qemu-devel] [PATCH] virtio-balloon: fix QEMU 4.0 config size migration incompatibility Stefan Hajnoczi 2019-07-10 15:24 ` Dr. David Alan Gilbert 2019-07-11 7:18 ` Wolfgang Bumiller 2019-07-11 8:30 ` Dr. David Alan Gilbert 2019-07-12 15:36 ` [Qemu-devel] [PULL 3/8] " Michael S. Tsirkin 2019-07-12 15:36 ` [Qemu-devel] [PULL 1/8] xio3130_downstream: typo fix Michael S. Tsirkin 2019-07-12 15:36 ` [Qemu-devel] [PULL 2/8] pcie: consistent names for function args Michael S. Tsirkin 2019-07-15 8:45 ` [Qemu-devel] [PULL 0/8] virtio, pc, pci: fixes, cleanups, tests Peter Maydell 2019-07-08 9:24 [Qemu-devel] [PATCH v3 0/2] tests: acpi: improve tests reproducability Igor Mammedov 2019-07-08 9:24 ` [Qemu-devel] [PATCH v3 1/2] tests: acpi: do not require IASL for dumping AML blobs Igor Mammedov 2019-07-12 15:36 ` [Qemu-devel] [PULL 4/8] " Michael S. Tsirkin 2019-07-08 9:24 ` [Qemu-devel] [PATCH v3 2/2] tests: acpi: do not skip tests when IASL is not installed Igor Mammedov 2019-07-12 15:36 ` [Qemu-devel] [PULL 5/8] " Michael S. Tsirkin
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=20190712073554.21918-3-pagupta@redhat.com \ --to=pagupta@redhat.com \ --cc=cohuck@redhat.com \ --cc=david@redhat.com \ --cc=mst@redhat.com \ --cc=peter.maydell@linaro.org \ --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: linkBe 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).