From: Leon Romanovsky <leon@kernel.org>
To: Hyong Youb Kim <hyonkim@cisco.com>
Cc: saeedm@nvidia.com, netdev@vger.kernel.org, kuba@kernel.org,
davem@davemloft.net, aviadye@mellanox.com,
steffen.klassert@secunet.com, Raed Salem <raeds@nvidia.com>
Subject: Re: [PATCH] net/mlx5e: Do not increment ESN when updating IPsec ESN state
Date: Mon, 29 Aug 2022 10:04:43 +0300 [thread overview]
Message-ID: <YwxlC5XrXchGWUUX@unreal> (raw)
In-Reply-To: <20220822052551.26903-1-hyonkim@cisco.com>
On Sun, Aug 21, 2022 at 10:25:51PM -0700, Hyong Youb Kim wrote:
> An offloaded SA stops receiving after about 2^32 + replay_window
> packets. For example, when SA reaches <seq-hi 0x1, seq 0x2c>, all
> subsequent packets get dropped with SA-icv-failure (integrity_failed).
>
> To reproduce the bug:
> - ConnectX-6 Dx with crypto enabled (FW 22.30.1004)
> - ipsec.conf:
> nic-offload = yes
> replay-window = 32
> esn = yes
> salifetime=24h
> - Run netperf for a long time to send more than 2^32 packets
> netperf -H <device-under-test> -t TCP_STREAM -l 20000
>
> When 2^32 + replay_window packets are received, the replay window
> moves from the 2nd half of subspace (overlap=1) to the 1st half
> (overlap=0). The driver then updates the 'esn' value in NIC
> (i.e. seq_hi) as follows.
>
> seq_hi = xfrm_replay_seqhi(seq_bottom)
> new esn in NIC = seq_hi + 1
>
> The +1 increment is wrong, as seq_hi already contains the correct
> seq_hi. For example, when seq_hi=1, the driver actually tells NIC to
> use seq_hi=2 (esn). This incorrect esn value causes all subsequent
> packets to fail integrity checks (SA-icv-failure). So, do not
> increment.
>
> Fixes: cb01008390bb ("net/mlx5: IPSec, Add support for ESN")
> Signed-off-by: Hyong Youb Kim <hyonkim@cisco.com>
> ---
> drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.c | 3 ---
> 1 file changed, 3 deletions(-)
>
Thanks,
Acked-by: Leon Romanovsky <leonro@nvidia.com>
prev parent reply other threads:[~2022-08-29 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 5:25 [PATCH] net/mlx5e: Do not increment ESN when updating IPsec ESN state Hyong Youb Kim
2022-08-29 7:04 ` Leon Romanovsky [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=YwxlC5XrXchGWUUX@unreal \
--to=leon@kernel.org \
--cc=aviadye@mellanox.com \
--cc=davem@davemloft.net \
--cc=hyonkim@cisco.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raeds@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=steffen.klassert@secunet.com \
/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