From: Kevin Traynor <ktraynor@redhat.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: stable@dpdk.org
Subject: Re: [PATCH 21.11 v2 1/2] crypto/ipsec_mb: fix length and offset settings
Date: Wed, 23 Mar 2022 16:14:05 +0000 [thread overview]
Message-ID: <da97bfcb-4748-cbda-2062-a48700e914c8@redhat.com> (raw)
In-Reply-To: <20220322151447.718221-1-pablo.de.lara.guarch@intel.com>
On 22/03/2022 15:14, Pablo de Lara wrote:
> [ upstream commit a501609ea6466ed8526c0dfadedee332a4d4a451 ]
>
> KASUMI, SNOW3G and ZUC require lengths and offsets to
> be set in bits or bytes depending on the algorithm.
> There were some algorithms that were mixing these two,
> so this commit is fixing this issue.
>
> Fixes: ae8e085c608d ("crypto/aesni_mb: support KASUMI F8/F9")
> Fixes: 6c42e0cf4d12 ("crypto/aesni_mb: support SNOW3G-UEA2/UIA2")
> Fixes: fd8df85487c4 ("crypto/aesni_mb: support ZUC-EEA3/EIA3")
> Fixes: 8c835018de84 ("crypto/ipsec_mb: support ZUC-256 for aesni_mb")
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
Thanks Pablo. Just to confirm, for 21.11 branch I will:
- revert previous backport of this 1/2 patch
- apply this series
Let me know if that is correct.
Kevin.
next prev parent reply other threads:[~2022-03-23 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 15:14 Pablo de Lara
2022-03-22 15:14 ` [PATCH 21.11 v2 2/2] crypto/ipsec_mb: fix GMAC parameters setting Pablo de Lara
2022-03-23 16:14 ` Kevin Traynor [this message]
2022-03-25 15:07 ` [PATCH 21.11 v2 1/2] crypto/ipsec_mb: fix length and offset settings Kevin Traynor
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=da97bfcb-4748-cbda-2062-a48700e914c8@redhat.com \
--to=ktraynor@redhat.com \
--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).