From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yong Wang <wang.yong19@zte.com.cn>,
hemant.agrawal@nxp.com, shreyansh.jain@nxp.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] net/dpaa: add null point check and fix mem leak
Date: Fri, 19 Jan 2018 19:38:39 +0000 [thread overview]
Message-ID: <95dc37b3-eb5b-dc2a-1d86-9d7116685023@intel.com> (raw)
In-Reply-To: <1516276136-618-1-git-send-email-wang.yong19@zte.com.cn>
On 1/18/2018 11:48 AM, Yong Wang wrote:
> There are several func calls to rte_zmalloc() which don't do null
> point check on the return value. And before return, the memory is not
> freed. Fix it by adding null point check and rte_free().
Fixes: 37f9b54bd3cf ("net/dpaa: support Tx and Rx queue setup")
Fixes: 62f53995caaf ("net/dpaa: add frame count based tail drop with CGR")
Cc: stable@dpdk.org
> Signed-off-by: Yong Wang <wang.yong19@zte.com.cn>
Reviewed-By: Shreyansh Jain <shreyansh.jain@nxp.com>
(carried from previous version of the patch)
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2018-01-19 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 11:48 Yong Wang
2018-01-19 19:38 ` Ferruh Yigit [this message]
[not found] <d0f656f30f9119b5823ce10d33af474ccf54f3e9>
2018-01-18 11:46 ` Yong Wang
[not found] <deddd4c>
2018-01-18 11:36 ` Yong Wang
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=95dc37b3-eb5b-dc2a-1d86-9d7116685023@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=shreyansh.jain@nxp.com \
--cc=wang.yong19@zte.com.cn \
/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).