patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <>
To: Pablo de Lara <>,,
Subject: Re: [PATCH 20.11 1/2] crypto/ipsec_mb: fix length and offset settings
Date: Tue, 15 Mar 2022 11:10:31 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Pablo,

On 14/03/2022 11:05, 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")
> Signed-off-by: Pablo de Lara <>
> ---

For 21.11. I backported and applied a501609ea6466 from dpdk main branch 
to 21.11 branch [0]. The version sent here directly to 20.11 is quite 
different as it adds the 'switch (job->cipher_mode)'. (It feels like 
some other patch adding 'switch (job->cipher_mode)' was missed for 

As this switch is not in [0], the following GMAC patch [1] won't apply 
for 21.11.

One option is that you send a patch to just add the missing parts, and 
then I apply the GMAC patch.

But the simplest option is that I revert [0], apply updated 20.11 
version + GMAC patch.

I'll go with the latter option (assuming they apply cleanly), but please 
let me know if that sounds ok.



[1] 837269c2e5c5 ("crypto/ipsec_mb: fix GMAC parameters setting")

  parent reply	other threads:[~2022-03-15 11:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 11:05 Pablo de Lara
2022-03-14 11:05 ` [PATCH 20.11 2/2] crypto/ipsec_mb: fix GMAC parameters setting Pablo de Lara
2022-03-14 12:20 ` [PATCH 20.11 1/2] crypto/ipsec_mb: fix length and offset settings Luca Boccassi
2022-03-21 19:57   ` De Lara Guarch, Pablo
2022-03-21 22:12     ` Luca Boccassi
2022-03-22 10:39       ` Kevin Traynor
2022-03-22 12:25         ` De Lara Guarch, Pablo
2022-03-15 11:10 ` Kevin Traynor [this message]
2022-03-15 11:18   ` Kevin Traynor
2022-03-21 20:02     ` De Lara Guarch, Pablo
2022-03-22 10:39       ` Kevin Traynor
2022-03-22 13:39 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).