From: Kevin Traynor <ktraynor@redhat.com>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>, stable@dpdk.org
Cc: jerinj@marvell.com, anoobj@marvell.com, ktejasree@marvell.com,
Akhil Goyal <gakhil@marvell.com>
Subject: Re: [PATCH 21.11] common/cnxk: fix auth key length
Date: Tue, 21 Mar 2023 16:20:18 +0000 [thread overview]
Message-ID: <707fd870-0683-968c-1b6a-d2a5d6816ba6@redhat.com> (raw)
In-Reply-To: <20230320170305.167316-1-gmuthukrishn@marvell.com>
On 20/03/2023 17:03, Gowrishankar Muthukrishnan wrote:
> [ upstream commit 0fcaf90fe25ecaa002d765fa9759e554500e3f76 ]
>
> Auth key length is stored as 8 bit value in SE context. It should
> be larger enough to accommodate supported auth key length of 1024
> bytes maximum, as in HMAC.
>
> Fixes: a45859312ff ("common/cnxk: add SE definitions for symmetric crypto")
>
> Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> ---
> drivers/common/cnxk/roc_se.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Thanks Gowri. Queued this for 21.11 pending CI pass.
Kevin.
prev parent reply other threads:[~2023-03-21 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 17:03 Gowrishankar Muthukrishnan
2023-03-21 16:20 ` Kevin Traynor [this message]
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=707fd870-0683-968c-1b6a-d2a5d6816ba6@redhat.com \
--to=ktraynor@redhat.com \
--cc=anoobj@marvell.com \
--cc=gakhil@marvell.com \
--cc=gmuthukrishn@marvell.com \
--cc=jerinj@marvell.com \
--cc=ktejasree@marvell.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).