DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	 "Xing, Beilei" <beilei.xing@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: fix NULL pointer dereferencing issue
Date: Thu, 7 May 2020 16:02:34 +0530	[thread overview]
Message-ID: <CAH-L+nPE95aQ+pFf6EKT9yL7qKsJfxjzrcxh+PGi9psVnLXYJw@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB2537230CE34028A3D69C1B1FEFA50@DM6PR11MB2537.namprd11.prod.outlook.com>

Hi Bernard,

On Thu, May 7, 2020 at 3:18 PM Iremonger, Bernard <
bernard.iremonger@intel.com> wrote:

> Hi Kalesh,
>
> > -----Original Message-----
> > From: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
> > Sent: Thursday, May 7, 2020 10:08 AM
> > To: dev@dpdk.org
> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Xing, Beilei
> > <beilei.xing@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>;
> Iremonger,
> > Bernard <bernard.iremonger@intel.com>
> > Subject: [dpdk-dev] [PATCH] app/testpmd: fix NULL pointer dereferencing
> > issue
> >
> > From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> >
> > Note that the issue was observed in an internal Coverity scan.
> >
> > Fixes: e088907bb851 ("app/testpmd: add command for getting loaded DDP
> > profiles")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> > ---
> >  app/test-pmd/cmdline.c | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/app/test-pmd/cmdline.c b/app/test-pmd/cmdline.c index
> > b040630..996a498 100644
> > --- a/app/test-pmd/cmdline.c
> > +++ b/app/test-pmd/cmdline.c
> > @@ -16891,8 +16891,10 @@ cmd_ddp_get_list_parsed(  #ifdef
> > RTE_LIBRTE_I40E_PMD
> >       size = PROFILE_INFO_SIZE * MAX_PROFILE_NUM + 4;
> >       p_list = (struct rte_pmd_i40e_profile_list *)malloc(size);
> > -     if (!p_list)
> > +     if (!p_list) {
> >               printf("%s: Failed to malloc buffer\n", __func__);
> > +             return;
> > +     }
> >
> >       if (ret == -ENOTSUP)
> >               ret = rte_pmd_i40e_get_ddp_list(res->port_id,
> > --
> > 2.10.1
>
> ./devtools/check-git-log.sh -1
> Wrong headline case:
> "app/testpmd: fix NULL pointer dereferencing issue": NULL --> null
>
[Kalesh]: will fix it.

> Missing 'Coverity issue:' tag:
>         app/testpmd: fix NULL pointer dereferencing issue
>
[Kalesh]:  This was found in an internal scan. So there is no Coverity
issue tag for this.

>
> Regards,
>
> Bernard.
>


-- 
Regards,
Kalesh A P

  reply	other threads:[~2020-05-07 10:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07  9:08 Kalesh A P
2020-05-07  9:48 ` Iremonger, Bernard
2020-05-07 10:32   ` Kalesh Anakkur Purayil [this message]
2020-05-07 10:43     ` Iremonger, Bernard
2020-05-07 11:06 ` [dpdk-dev] [PATCH v2] app/testpmd: fix null " Kalesh A P
2020-05-07 13:21   ` Iremonger, Bernard
2020-05-08  4:50   ` [dpdk-dev] [PATCH v3] " Kalesh A P
2020-05-08 15:13     ` Ferruh Yigit

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=CAH-L+nPE95aQ+pFf6EKT9yL7qKsJfxjzrcxh+PGi9psVnLXYJw@mail.gmail.com \
    --to=kalesh-anakkur.purayil@broadcom.com \
    --cc=beilei.xing@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jingjing.wu@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).