From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] crypto/aesni_mb: fix possible crypto job leak
Date: Thu, 13 Jul 2017 16:34:36 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CBDB8D4@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <3a49844a-e31b-d8fe-d1ef-0c03778bba56@intel.com>
> -----Original Message-----
> From: Doherty, Declan
> Sent: Thursday, July 13, 2017 4:56 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: Re: [PATCH] crypto/aesni_mb: fix possible crypto job leak
>
> On 13/07/2017 4:35 AM, Pablo de Lara wrote:
> > When dequeueing operations from an AESNI-MB device, crypto jobs are
> > dequeued from the internal scheduler in the Multi-buffer library.
> >
> > If the number of jobs available to retrieve are higher than the number
> > of crypto operations that are required, then an extra job is retrieved
> > (due to an incorrect conditional), but not used.
> > This leads to a job leak and the operation associated to that job will
> > not be ever dequeued.
> >
> > Fixes: 0f548b50a160 ("crypto/aesni_mb: process crypto op on dequeue")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> > ---
>
> ...
> >
>
> Acked-by: Declan Doherty <declan.doherty@intel.com>
Applied to dpdk-next-crypto.
Pablo
prev parent reply other threads:[~2017-07-13 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 3:35 Pablo de Lara
2017-07-13 15:56 ` Declan Doherty
2017-07-13 16:34 ` 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=E115CCD9D858EF4F90C690B0DCB4D8976CBDB8D4@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).