From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Andy Pei <andy.pei@intel.com>, dev@dpdk.org
Cc: chenbo.xia@intel.com, xiao.w.wang@intel.com
Subject: Re: [PATCH] vdpa/ifc/base: fix null pointer dereference
Date: Fri, 8 Jul 2022 10:51:26 +0200 [thread overview]
Message-ID: <6b4afd2b-3fc2-3e60-5346-579f1b243ffa@redhat.com> (raw)
In-Reply-To: <1657259861-75138-1-git-send-email-andy.pei@intel.com>
On 7/8/22 07:57, Andy Pei wrote:
> Fix null pointer dereference reported in coverity scan.
> Output some log information when lm_cfg is null.
> Make lm_cfg is not null before operate on lm_cfg.
Make sure*
>
> Coverity issue: 378882
> Fixes: d7fe5a2861e7 ("net/ifc: support live migration")
>
> Signed-off-by: Andy Pei <andy.pei@intel.com>
> ---
> drivers/vdpa/ifc/base/ifcvf.c | 31 ++++++++++++++++++++-----------
> drivers/vdpa/ifc/base/ifcvf_osdep.h | 1 +
> 2 files changed, 21 insertions(+), 11 deletions(-)
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2022-07-08 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 5:57 Andy Pei
2022-07-08 8:51 ` Maxime Coquelin [this message]
2022-07-08 9:11 ` Maxime Coquelin
2022-07-08 9:17 ` Pei, Andy
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=6b4afd2b-3fc2-3e60-5346-579f1b243ffa@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=andy.pei@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=xiao.w.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).