From: sashiko-bot@kernel.org
To: "Tariq Toukan" <tariqt@nvidia.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH net] net/mlx5e: Fix XSK pool corruption when switching channels
Date: Sun, 15 Nov 2026 07:42:24 +0000 [thread overview]
Message-ID: <sashiko-outbox-215266@kernel.org> (raw)
In-Reply-To: <20261115072934.353341-1-tariqt@nvidia.com>
> From: Gal Pressman <gal@nvidia.com>
>
> When the device supports tis_tir_td_order, mlx5e_safe_switch_params()
> closes the old channels only after the new ones are activated. With an
> AF_XDP socket bound, the old and the new channel hold an XSK RQ on the
> same pool.
>
> The old RQ returns its buffers to the pool while the new RQ is already
> allocating from it. Since the pool is lockless and expects a single user
> at a time, it gets out of sync.
>
> Close the old XSK queues before activating the new channels, the rest of
> the old channels can still be closed later.
>
> The crash was hit by our regression tests, with a random sequence of
> [ ... ]
>
> Fixes: 3b88a535a8e1 ("net/mlx5e: Defer channels closure to reduce interface down time")
> Signed-off-by: Gal Pressman <gal@nvidia.com>
> Reviewed-by: Nimrod Oren <noren@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261115072934.353341-1-tariqt@nvidia.com?part=1
prev parent reply other threads:[~2026-11-15 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 7:29 [PATCH net] net/mlx5e: Fix XSK pool corruption when switching channels Tariq Toukan
2026-11-15 7:42 ` sashiko-bot [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=sashiko-outbox-215266@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tariqt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.