From: Tiwei Bie <tiwei.bie@intel.com>
To: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
Cc: dev@dpdk.org, maxime.coquelin@redhat.com, zhihong.wang@intel.com,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] vhost: fix null pointer checking
Date: Mon, 8 Apr 2019 11:38:45 +0800 [thread overview]
Message-ID: <20190408033845.GC20719@dpdk-tbie.sh.intel.com> (raw)
Message-ID: <20190408033845._uo9Jsalbtq7gg1etDjeVbxsmaDijfbGXI8rbOAv-y0@z> (raw)
In-Reply-To: <20190404085317.32337-1-mohammad.abdul.awal@intel.com>
On Thu, Apr 04, 2019 at 09:53:17AM +0100, Mohammad Abdul Awal wrote:
> Null value for parameters will cause segfault.
>
> Fixes: d7280c9fff ("vhost: support selective datapath")
> Fixes: 72e8543093df ("vhost: add API to get MTU value")
> Fixes: a277c71598 ("vhost: refactor code structure")
> Fixes: ca33faf9ef ("vhost: introduce API to fetch negotiated features")
> Fixes: eb32247457 ("vhost: export guest memory regions")
> Fixes: 40ef286f23 ("vhost: export vhost vring info")
> Fixes: bd2e0c3fe5 ("vhost: add APIs for live migration")
> Fixes: 0b8572a0c1 ("vhost: add external message handling to the API")
> Fixes: b4953225ce ("vhost: add APIs for datapath configuration")
Would be better to use the same length (12) for hashes.
> Cc: stable@dpdk.org
>
> Signed-off-by: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
> ---
> lib/librte_vhost/socket.c | 2 +-
> lib/librte_vhost/vdpa.c | 5 ++++-
> lib/librte_vhost/vhost.c | 16 ++++++++--------
> 3 files changed, 13 insertions(+), 10 deletions(-)
>
> diff --git a/lib/librte_vhost/socket.c b/lib/librte_vhost/socket.c
> index 3da9de62c..a89665946 100644
> --- a/lib/librte_vhost/socket.c
> +++ b/lib/librte_vhost/socket.c
> @@ -562,7 +562,7 @@ rte_vhost_driver_attach_vdpa_device(const char *path, int did)
> {
> struct vhost_user_socket *vsocket;
>
> - if (rte_vdpa_get_device(did) == NULL)
> + if (rte_vdpa_get_device(did) == NULL || path == NULL)
There are multiple APIs accepting `path` parameter without
validating it in socket.c. I meant we can do the check for
most of them in find_vhost_user_socket():
https://github.com/DPDK/dpdk/blob/bdcfcceb7a0b7534a0dba669279d18bd0f98d5e5/lib/librte_vhost/socket.c#L546
For the cases which can't be covered by the check in
find_vhost_user_socket(), we need to do the check separately,
e.g.:
https://github.com/DPDK/dpdk/blob/bdcfcceb7a0b7534a0dba669279d18bd0f98d5e5/lib/librte_vhost/socket.c#L972
For the rest,
Reviewed-by: Tiwei Bie <tiwei.bie@intel.com>
Thanks!
Tiwei
next prev parent reply other threads:[~2019-04-08 3:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 8:53 Mohammad Abdul Awal
2019-04-04 8:53 ` Mohammad Abdul Awal
2019-04-08 3:38 ` Tiwei Bie [this message]
2019-04-08 3:38 ` Tiwei Bie
2019-04-17 7:13 ` Maxime Coquelin
2019-04-17 7:13 ` 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=20190408033845.GC20719@dpdk-tbie.sh.intel.com \
--to=tiwei.bie@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=mohammad.abdul.awal@intel.com \
--cc=stable@dpdk.org \
--cc=zhihong.wang@intel.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).