From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>, "mkp@redhat.com" <mkp@redhat.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: RE: [PATCH] vhost: fix possible null pointer dereference
Date: Fri, 10 Mar 2023 02:52:34 +0000 [thread overview]
Message-ID: <SN6PR11MB35046526B132993C4909C0019CBA9@SN6PR11MB3504.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230309113631.300351-1-maxime.coquelin@redhat.com>
> -----Original Message-----
> From: Maxime Coquelin <maxime.coquelin@redhat.com>
> Sent: Thursday, March 9, 2023 7:37 PM
> To: dev@dpdk.org; mkp@redhat.com; Xia, Chenbo <chenbo.xia@intel.com>;
> david.marchand@redhat.com
> Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
> Subject: [PATCH] vhost: fix possible null pointer dereference
>
> When handling VHOST_USER_SET_MEM_TABLE request ending
> up in changing existing memory map, a device's memory
> pointer may ends up being dereference while being NULL in
> IOTLB cache flush function.
>
> Coverity issue: 383646
> Fixes: dea092d0addb ("vhost: fix madvise arguments alignment")
>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
> lib/vhost/vhost_user.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/lib/vhost/vhost_user.c b/lib/vhost/vhost_user.c
> index 9e361082dc..23a6a4e2bd 100644
> --- a/lib/vhost/vhost_user.c
> +++ b/lib/vhost/vhost_user.c
> @@ -1355,16 +1355,16 @@ vhost_user_set_mem_table(struct virtio_net **pdev,
> async_notify = true;
> }
>
> + /* Flush IOTLB cache as previous HVAs are now invalid */
> + if (dev->features & (1ULL << VIRTIO_F_IOMMU_PLATFORM))
> + for (i = 0; i < dev->nr_vring; i++)
> + vhost_user_iotlb_flush_all(dev, dev->virtqueue[i]);
> +
> free_mem_region(dev);
> rte_free(dev->mem);
> dev->mem = NULL;
> }
>
> - /* Flush IOTLB cache as previous HVAs are now invalid */
> - if (dev->features & (1ULL << VIRTIO_F_IOMMU_PLATFORM))
> - for (i = 0; i < dev->nr_vring; i++)
> - vhost_user_iotlb_flush_all(dev, dev->virtqueue[i]);
> -
> /*
> * If VQ 0 has already been allocated, try to allocate on the same
> * NUMA node. It can be reallocated later in numa_realloc().
> --
> 2.39.2
Reviewed-by: Chenbo Xia <chenbo.xia@intel.com>
next prev parent reply other threads:[~2023-03-10 2:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 11:36 Maxime Coquelin
2023-03-10 2:52 ` Xia, Chenbo [this message]
2023-03-16 14:47 ` Maxime Coquelin
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=SN6PR11MB35046526B132993C4909C0019CBA9@SN6PR11MB3504.namprd11.prod.outlook.com \
--to=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=mkp@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).