Netdev List
 help / color / mirror / Atom feed
From: Jerome Tollet <jtollet@cisco.com>
To: stable@vger.kernel.org
Cc: netdev@vger.kernel.org, kuba@kernel.org, dtatulea@nvidia.com
Subject: [stable] Please consider two mlx5e AF_XDP refill fixes
Date: Thu, 08 Oct 2026 16:56:54 +0200	[thread overview]
Message-ID: <179147141500.99533.12861786180147681790@cisco.com> (raw)

Hi,

Could you please pick up these two upstream fixes for the affected
stable trees, including 7.2.y, 6.18.y and 6.12.y?

  e01620844c5c88b6fcf819d171df8e3976a0e76f
  net/mlx5e: Prevent stale XSK buffer release on refill retry

  63811edf512584c946e5e96b100e9e280703bbb5
  net/mlx5e: Prevent stale XSK buffer release on MPWQE refill retry

Both are in mainline since 7.3-rc2 and carry Fixes and Cc: stable tags.
They prevent repeated release of stale AF_XDP buffers after RX refill
failures, causing silent UMEM ownership errors.

I checked 7.2.9, 6.18.55, 6.12.112 and their stable queues: neither fix
is present. Please let me know if backport adjustments are needed.

Original series:
https://lore.kernel.org/netdev/20260824141645.23700-1-jtollet@cisco.com/

Thanks,
Jerome

                 reply	other threads:[~2026-10-08 14:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=179147141500.99533.12861786180147681790@cisco.com \
    --to=jtollet@cisco.com \
    --cc=dtatulea@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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