patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2 2/9] test/crypto: fix wrong AAD setting
Date: Fri, 23 Jun 2017 09:56:40 +0000	[thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435892224DB@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20170622120235.46063-3-pablo.de.lara.guarch@intel.com>



> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Thursday, June 22, 2017 1:02 PM
> To: Doherty, Declan <declan.doherty@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>
> Cc: dev@dpdk.org; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; stable@dpdk.org
> Subject: [PATCH v2 2/9] test/crypto: fix wrong AAD setting
> 
> AAD should not point at IV for AES algorithms.
> For AES-GCM, AAD will point at additional data in the mbuf.
> For the other algorithms (such as 3DES CBC), AAD is not used.
> 
> Fixes: ffbe3be0d4b5 ("app/test: add libcrypto")
> CC: stable@dpdk.org
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>

  reply	other threads:[~2017-06-23  9:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170621064154.25124-1-pablo.de.lara.guarch@intel.com>
2017-06-21  6:41 ` [dpdk-stable] [PATCH 1/9] crypto/aesni_mb: remove assert check Pablo de Lara
2017-06-21  6:41 ` [dpdk-stable] [PATCH 2/9] test/crypto: fix wrong AAD setting Pablo de Lara
2017-06-21 17:39   ` [dpdk-stable] [dpdk-dev] " Trahe, Fiona
2017-06-22 10:40     ` De Lara Guarch, Pablo
2017-06-21  6:41 ` [dpdk-stable] [PATCH 6/9] examples/l2fwd-crypto: fix application help Pablo de Lara
2017-06-21 16:43   ` [dpdk-stable] [dpdk-dev] " Trahe, Fiona
2017-06-21  6:41 ` [dpdk-stable] [PATCH 7/9] examples/l2fwd-crypto: fix auth info display Pablo de Lara
2017-06-21 16:44   ` [dpdk-stable] [dpdk-dev] " Trahe, Fiona
2017-06-21  6:41 ` [dpdk-stable] [PATCH 8/9] app/crypto-perf: fix error message Pablo de Lara
2017-06-21 16:39   ` [dpdk-stable] [dpdk-dev] " Trahe, Fiona
2017-06-21  6:41 ` [dpdk-stable] [PATCH 9/9] doc: fix typo in l2fwd-crypto usage Pablo de Lara
2017-06-21 17:44   ` [dpdk-stable] [dpdk-dev] " Trahe, Fiona
     [not found] ` <20170622120235.46063-1-pablo.de.lara.guarch@intel.com>
2017-06-22 12:02   ` [dpdk-stable] [PATCH v2 1/9] crypto/aesni_mb: remove assert check Pablo de Lara
2017-06-23 12:50     ` Declan Doherty
2017-06-22 12:02   ` [dpdk-stable] [PATCH v2 2/9] test/crypto: fix wrong AAD setting Pablo de Lara
2017-06-23  9:56     ` Trahe, Fiona [this message]
2017-06-22 12:02   ` [dpdk-stable] [PATCH v2 6/9] examples/l2fwd-crypto: fix application help Pablo de Lara
2017-06-22 12:02   ` [dpdk-stable] [PATCH v2 7/9] examples/l2fwd-crypto: fix auth info display Pablo de Lara
2017-06-22 12:02   ` [dpdk-stable] [PATCH v2 8/9] app/crypto-perf: fix error message Pablo de Lara
2017-06-22 12:02   ` [dpdk-stable] [PATCH v2 9/9] doc: fix typo in l2fwd-crypto usage Pablo de Lara

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=348A99DA5F5B7549AA880327E580B435892224DB@IRSMSX101.ger.corp.intel.com \
    --to=fiona.trahe@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@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).