DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>, dev@dpdk.org
Cc: beilei.xing@intel.com, jingjing.wu@intel.com,
	bernard.iremonger@intel.com
Subject: Re: [dpdk-dev] [PATCH v3] app/testpmd: fix null pointer dereferencing issue
Date: Fri, 8 May 2020 16:13:10 +0100	[thread overview]
Message-ID: <184ad59a-b4f8-1933-95ab-cea48fb141a4@intel.com> (raw)
In-Reply-To: <20200508045024.19739-1-kalesh-anakkur.purayil@broadcom.com>

On 5/8/2020 5:50 AM, Kalesh A P wrote:
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> 
> In cmd_ddp_get_list_parsed(), elements of "p_list" are accessed
> even after the memory allocation for "p_list" fails.
> 
> With this patch, this null pointer dereference is avoided as we
> return when there is malloc failure.
> 
> 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>
> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2020-05-08 15:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07  9:08 [dpdk-dev] [PATCH] app/testpmd: fix NULL " Kalesh A P
2020-05-07  9:48 ` Iremonger, Bernard
2020-05-07 10:32   ` Kalesh Anakkur Purayil
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 [this message]

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=184ad59a-b4f8-1933-95ab-cea48fb141a4@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=kalesh-anakkur.purayil@broadcom.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).