From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
gregkh@linuxfoundation.org, saeedm@nvidia.com,
netdev@vger.kernel.org, phaddad@nvidia.com,
Dragos Tatulea <dtatulea@nvidia.com>, Paul Saab <ps@mu.org>,
Tariq Toukan <tariqt@nvidia.com>, Simon Horman <horms@kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH v2 6.1.y 6.6.y 6.12.y 6.18.y] net/mlx5e: xsk: Fix unlocked writing to ICOSQ
Date: Wed, 9 Sep 2026 16:26:01 -0400 [thread overview]
Message-ID: <2026-09-09-daily-reply-0003-mlx5e-xsk-icosq@kernel.org> (raw)
In-Reply-To: <20260909141332.2297825-2-dtatulea@nvidia.com>
> During napi poll, when the affinity changes and there's still XSK work
> to be done, we trigger an ICOSQ interrupt on the new CPU. However, this
> triggering on the ICOSQ is done unprotected.
Queued for 6.18, 6.12, 6.6 and 6.1, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-09-09 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 14:13 [PATCH v2 6.1.y 6.6.y 6.12.y 6.18.y] net/mlx5e: xsk: Fix unlocked writing to ICOSQ Dragos Tatulea
2026-09-09 20:26 ` Sasha Levin [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=2026-09-09-daily-reply-0003-mlx5e-xsk-icosq@kernel.org \
--to=sashal@kernel.org \
--cc=dtatulea@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=phaddad@nvidia.com \
--cc=ps@mu.org \
--cc=saeedm@nvidia.com \
--cc=stable@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox