From: Luca Boccassi <bluca@debian.org>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: stable@dpdk.org, Fan Zhang <roy.fan.zhang@intel.com>,
Radu Nicolau <radu.nicolau@intel.com>
Subject: Re: [PATCH 20.11 2/2] crypto/ipsec_mb: fix GMAC parameters setting
Date: Mon, 04 Apr 2022 14:35:03 +0100 [thread overview]
Message-ID: <c8b9490b6206ad035430b0af4b57b23429c918f0.camel@debian.org> (raw)
In-Reply-To: <20220322133910.664010-2-pablo.de.lara.guarch@intel.com>
On Tue, 2022-03-22 at 13:39 +0000, Pablo de Lara wrote:
> [ upstream commit 837269c2e5c5a8813adfcf59f23b80569048ddeb ]
> AES-GMAC requires plaintext length to be 0 when using AES-GCM,
> so only AAD data is used.
>
> Fixes: a501609ea646 ("crypto/ipsec_mb: fix length and offset settings")
> Cc: pablo.de.lara.guarch@intel.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
> Acked-by: Radu Nicolau <radu.nicolau@intel.com>
> Tested-by: Radu Nicolau <radu.nicolau@intel.com>
> ---
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 17 ++++++++++++++---
> 1 file changed, 14 insertions(+), 3 deletions(-)
Thanks, series queued for 20.11.6.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2022-04-04 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 13:39 [PATCH 20.11 1/2] crypto/ipsec_mb: fix length and offset settings Pablo de Lara
2022-03-22 13:39 ` [PATCH 20.11 2/2] crypto/ipsec_mb: fix GMAC parameters setting Pablo de Lara
2022-04-04 13:35 ` Luca Boccassi [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-14 11:05 [PATCH 20.11 1/2] crypto/ipsec_mb: fix length and offset settings Pablo de Lara
2022-03-14 11:05 ` [PATCH 20.11 2/2] crypto/ipsec_mb: fix GMAC parameters setting 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=c8b9490b6206ad035430b0af4b57b23429c918f0.camel@debian.org \
--to=bluca@debian.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@intel.com \
--cc=roy.fan.zhang@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).