From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Zhoujian (jay)" <jianjay.zhou@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"wangxin (U)" <wangxinxin.wang@huawei.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/virtio: fix memory leak
Date: Mon, 23 Jul 2018 09:40:59 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F8FF5A1@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <B2D15215269B544CADD246097EACE7473B70F6A1@DGGEMM528-MBX.china.huawei.com>
> -----Original Message-----
> From: Zhoujian (jay) [mailto:jianjay.zhou@huawei.com]
> Sent: Monday, July 23, 2018 8:45 AM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org; wangxin (U)
> <wangxinxin.wang@huawei.com>
> Subject: RE: [PATCH] crypto/virtio: fix memory leak
>
> > -----Original Message-----
> > From: Pablo de Lara [mailto:pablo.de.lara.guarch@intel.com]
> > Sent: Thursday, July 19, 2018 5:06 PM
> > To: Zhoujian (jay) <jianjay.zhou@huawei.com>
> > Cc: dev@dpdk.org; Pablo de Lara <pablo.de.lara.guarch@intel.com>;
> > stable@dpdk.org
> > Subject: [PATCH] crypto/virtio: fix memory leak
> >
> > Put session private data back to mempool when clearing a crypto
> > session, which is expected to be done in the PMD.
> >
> > Fixes: b7fa78c7d3b0 ("crypto/virtio: support session related ops")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
>
> Reviewed-by: Jay Zhou <jianjay.zhou@huawei.com>
Applied to dpdk-next-crypto.
Pablo
prev parent reply other threads:[~2018-07-23 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 9:05 Pablo de Lara
2018-07-23 7:44 ` Zhoujian (jay)
2018-07-23 9:40 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D8977F8FF5A1@IRSMSX107.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=jianjay.zhou@huawei.com \
--cc=stable@dpdk.org \
--cc=wangxinxin.wang@huawei.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).