DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Yong Wang <wang.yong19@zte.com.cn>
Cc: dev@dpdk.org, "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] crypto/qat: add null point check and fix mem leak
Date: Thu, 01 Feb 2018 00:33:41 +0100	[thread overview]
Message-ID: <5801381.qQ5GPbfyJT@xps> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B435893008D3@IRSMSX101.ger.corp.intel.com>

> > 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: 1703e94ac5ce ("qat: add driver for QuickAssist devices")
> > Fixes: e09231eaa2af ("crypto/qat: add SGL capability")
> > 
> > Signed-off-by: Yong Wang <wang.yong19@zte.com.cn>
> Acked-by: Fiona Trahe <fiona.trahe@intel.com>

Applied, thanks

      reply	other threads:[~2018-01-31 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25  6:53 Yong Wang
2018-01-25  9:52 ` Trahe, Fiona
2018-01-31 23:33   ` Thomas Monjalon [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=5801381.qQ5GPbfyJT@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.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).