[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <15d65b5f-aa90-d2b9-cb17-9b29b463fe0f@nvidia.com>
Date: Tue, 20 Sep 2022 12:40:05 +0300
From: Gal Pressman <gal@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Saeed Mahameed <saeedm@...dia.com>,
Tariq Toukan <tariqt@...dia.com>
Subject: Re: [PATCH net-next 4/4] net/mlx5e: Support 256 bit keys with kTLS
device offload
On 20/09/2022 04:47, Jakub Kicinski wrote:
> On Wed, 14 Sep 2022 12:05:20 +0300 Gal Pressman wrote:
>> spin_lock_bh(&ktls_resync->lock);
>> spin_lock_bh(&priv_rx->lock);
>> - memcpy(info->rec_seq, &priv_rx->resync.sw_rcd_sn_be, sizeof(info->rec_seq));
>> + switch (priv_rx->crypto_info.crypto_info.cipher_type) {
>> + case TLS_CIPHER_AES_GCM_128: {
> ...
>
>> + default:
>> + WARN_ONCE(1, "Unsupported cipher type %u\n",
>> + priv_rx->crypto_info.crypto_info.cipher_type);
>> + return;
> Sparse suggests releasing the locks.
Ugh, will check how it was missed in our CI, thanks.
Powered by blists - more mailing lists