mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tariq Toukan <tariqt@nvidia.com>
To: Jiabin Deng <dengjiabin2023@gmail.com>, netdev@vger.kernel.org
Cc: Dragos Tatulea <dtatulea@nvidia.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
	Leon Romanovsky <leon@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net/mlx5e: SHAMPO, Disable end padding when relaxed ordering is supported
Date: Mon, 9 Nov 2026 14:29:19 +0200	[thread overview]
Message-ID: <529136c6-26af-4193-b887-92e0ad865544@nvidia.com> (raw)
In-Reply-To: <20261109034444.11241-1-dengjiabin2023@gmail.com>



On 09/11/2026 5:44, Jiabin Deng wrote:
> When SHAMPO and relaxed ordering writes are enabled, aligned RQ end
> padding can corrupt received TCP data. Due to reordering, alignment
> padding written at the end of one packet can overwrite data from the
> next packet.
> 
> The current RQ end padding selection avoids alignment padding for LRO,
> but not for SHAMPO. Extend the condition to SHAMPO to prevent this
> corruption.
> 
> The issue was observed in a two-host test using a BlueField-3 NIC and
> an NVIDIA H20 GPU. In the original test with MTU 1500, 354 of 400
> transfers contained corrupted data before the fix. After applying this
> change, all 400 transfers across eight message sizes from 32 KiB to
> 4 MiB, with 50 transfers per size, completed successfully, with no
> incorrect bytes or corrupted intervals.
> 
> Fixes: e5ca8fb08ab2 ("net/mlx5e: Add control path for SHAMPO feature")
> Closes: https://lists.openwall.net/linux-kernel/2026/09/15/154
> Link: https://lists.openwall.net/linux-kernel/2026/10/20/1322

nits:

lore.kernel.org links are preferred.

The Cc list leaves out the netdev maintainers and 
linux-rdma@vger.kernel.org (from MAINTAINERS for mlx5 core).


> Suggested-by: Dragos Tatulea <dtatulea@nvidia.com>
> Reviewed-by: Dragos Tatulea <dtatulea@nvidia.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Jiabin Deng <dengjiabin2023@gmail.com>
> ---
> Changes in v2:
> - Clarify that the corruption is not specific to GPU or DMA-BUF memory.
> - Explain how reordered alignment padding can overwrite the next
>    packet's data.
> - Add Dragos Tatulea's Reviewed-by tag.
> - No code changes.
> 
> v1: https://lore.kernel.org/netdev/20261106083719.22798-1-dengjiabin2023@gmail.com/
> 
>   drivers/net/ethernet/mellanox/mlx5/core/en/params.c | 5 +++--
>   1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en/params.c b/drivers/net/ethernet/mellanox/mlx5/core/en/params.c
> index 5caf7820a136..159f79302a08 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/en/params.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/en/params.c
> @@ -911,10 +911,11 @@ static void mlx5e_build_rx_cq_param(struct mlx5_core_dev *mdev,
>   
>   static u8 rq_end_pad_mode(struct mlx5_core_dev *mdev, struct mlx5e_params *params)
>   {
> -	bool lro_en = params->packet_merge.type == MLX5E_PACKET_MERGE_LRO;
> +	bool no_pad = params->packet_merge.type == MLX5E_PACKET_MERGE_LRO ||
> +		      params->packet_merge.type == MLX5E_PACKET_MERGE_SHAMPO;
>   	bool ro = MLX5_CAP_GEN(mdev, relaxed_ordering_write);
>   
> -	return ro && lro_en ?
> +	return ro && no_pad ?
>   		MLX5_WQ_END_PAD_MODE_NONE : MLX5_WQ_END_PAD_MODE_ALIGN;
>   }
>   

Thanks for the fix.

Reviewed-by: Tariq Toukan <tariqt@nvidia.com>

> 
> base-commit: fafbc4051123d5459ea6950899cec08ed946e278


      reply	other threads:[~2026-11-09 12:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09  3:44 Jiabin Deng
2026-11-09 12:29 ` Tariq Toukan [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=529136c6-26af-4193-b887-92e0ad865544@nvidia.com \
    --to=tariqt@nvidia.com \
    --cc=dengjiabin2023@gmail.com \
    --cc=dtatulea@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.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

all inboxes | Powered by JetHome®