From: "Pei, Andy" <andy.pei@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Xia, Chenbo" <chenbo.xia@intel.com>,
"Wang, Xiao W" <xiao.w.wang@intel.com>,
"Xu, Rosen" <rosen.xu@intel.com>,
"Xiao, QimaiX" <qimaix.xiao@intel.com>
Subject: RE: [PATCH v2] vdpa/ifc: fix null pointer dereference
Date: Sat, 18 Jun 2022 09:04:50 +0000 [thread overview]
Message-ID: <DM5PR11MB17397DCA8A0A2094BD62BF738FAE9@DM5PR11MB1739.namprd11.prod.outlook.com> (raw)
In-Reply-To: <65d3f014-5116-2137-2843-9344de2b8da1@redhat.com>
Hi Maxime,
Thanks for your effort.
> -----Original Message-----
> From: Maxime Coquelin <maxime.coquelin@redhat.com>
> Sent: Friday, June 17, 2022 10:08 PM
> To: Pei, Andy <andy.pei@intel.com>; dev@dpdk.org
> Cc: Xia, Chenbo <chenbo.xia@intel.com>; Wang, Xiao W
> <xiao.w.wang@intel.com>; Xu, Rosen <rosen.xu@intel.com>; Xiao, QimaiX
> <qimaix.xiao@intel.com>
> Subject: Re: [PATCH v2] vdpa/ifc: fix null pointer dereference
>
>
>
> On 6/15/22 08:23, Andy Pei wrote:
> > Fix null pointer dereference reported in coverity scan.
> >
> > Coverity issue: 378882
> > Fixes: 5d75517beffe ("vdpa/ifc/base: access correct register for blk device")
> >
> > Signed-off-by: Andy Pei <andy.pei@intel.com>
> > Acked-by: Xiao Wang <xiao.w.wang@intel.com>
> > ---
> > drivers/vdpa/ifc/base/ifcvf.c | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
>
> Applied to dpdk-next-virtio/main.
>
> Thanks,
> Maxime
next prev parent reply other threads:[~2022-06-18 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 7:34 [PATCH] " Andy Pei
2022-06-08 8:25 ` Wang, Xiao W
2022-06-15 2:04 ` Xia, Chenbo
2022-06-15 7:08 ` Pei, Andy
2022-06-15 6:23 ` [PATCH v2] " Andy Pei
2022-06-17 12:40 ` Maxime Coquelin
2022-06-17 14:07 ` Maxime Coquelin
2022-06-18 9:04 ` Pei, Andy [this message]
2022-06-15 6:16 Andy Pei
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=DM5PR11MB17397DCA8A0A2094BD62BF738FAE9@DM5PR11MB1739.namprd11.prod.outlook.com \
--to=andy.pei@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=qimaix.xiao@intel.com \
--cc=rosen.xu@intel.com \
--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).