From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Mrzyglod, DanielX T" <danielx.t.mrzyglod@intel.com>,
"Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Mrzyglod, DanielX T" <danielx.t.mrzyglod@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v3] app/crypto-perf: fix avoid wrong optype for AEAD algorithms
Date: Thu, 9 Mar 2017 21:46:21 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476EC0BD@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D897476EC086@IRSMSX108.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch,
> Pablo
> Sent: Thursday, March 09, 2017 9:35 PM
> To: Mrzyglod, DanielX T; Mrozowicz, SlawomirX; Doherty, Declan
> Cc: dev@dpdk.org; Mrzyglod, DanielX T
> Subject: Re: [dpdk-dev] [PATCH v3] app/crypto-perf: fix avoid wrong optype
> for AEAD algorithms
>
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Daniel Mrzyglod
> > Sent: Wednesday, March 08, 2017 5:03 PM
> > To: Mrozowicz, SlawomirX; Doherty, Declan; De Lara Guarch, Pablo
> > Cc: dev@dpdk.org; Mrzyglod, DanielX T
> > Subject: [dpdk-dev] [PATCH v3] app/crypto-perf: fix avoid wrong optype
> for
> > AEAD algorithms
> >
> > When somebody use bad --optype with aead alghorithms
> > segmentation fault could happen.
> >
> > Fixes: f8be1786b1b8 ("app/crypto-perf: introduce performance test
> > application")
> >
> > Signed-off-by: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
CC'ing stable list.
Applied to dpdk-next-crypto.
Thanks,
Pablo
parent reply other threads:[~2017-03-09 21:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E115CCD9D858EF4F90C690B0DCB4D897476EC086@IRSMSX108.ger.corp.intel.com>]
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=E115CCD9D858EF4F90C690B0DCB4D897476EC0BD@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=danielx.t.mrzyglod@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=slawomirx.mrozowicz@intel.com \
--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).