From: Joshua Washington <joshwash@google.com>
To: netdev@vger.kernel.org
Cc: Joshua Washington <joshwash@google.com>,
Harshitha Ramamurthy <hramamurthy@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jordan Rhee <jordanrhee@google.com>,
Willem de Bruijn <willemb@google.com>,
Ankit Garg <nktgrg@google.com>,
Tim Hostetler <thostet@google.com>,
Praveen Kaligineedi <pkaligineedi@google.com>,
Jeroen de Borst <jeroendb@google.com>,
Stanislav Fomichev <sdf@fomichev.me>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: [PATCH net 0/6] gve: various XDP fixes
Date: Fri, 14 Aug 2026 16:48:39 -0700 [thread overview]
Message-ID: <20260814234845.773189-1-joshwash@google.com> (raw)
This patch series includes a number of XDP-related fixes, both in the
control plane and the dataplane.
A summary of the changes:
1) fix an issue where XDP packets weren't being counted against NAPI
budget
2) fix an issue where XSK buffers that have not been processed are
leaked when disabling XSK pools
3) fix an XSK buffer leak when an RX error descriptor comes back from
the hardware
4) fix a NULL dereference due to incorrect registration of XSK pools on
queues not set up in XSK zero copy mode
5) fix a deadlock introduced by attempting to acquire the netdev lock
after it has already been acquired
6) fix a racy NULL dereference due to DMA umapping the XSK pool before
queues are fully stopped
Joshua Washington (6):
gve: increment work_done for XDP and error packets
gve: fix XSK buffer leak when rings are stopped
gve: fix XSK buffer leak on error descriptor
gve: don't register xsk pool on pre-existing queues in RDA mode
gve: fix napi_disable deadlock when attempting to disable XSK pools
gve: fix NULL dereference from premature XSK pool DMA unmap
drivers/net/ethernet/google/gve/gve_main.c | 51 ++++++++++----------
drivers/net/ethernet/google/gve/gve_rx_dqo.c | 20 ++++++--
2 files changed, 42 insertions(+), 29 deletions(-)
--
2.55.0.691.gc56d675ccc-goog
next reply other threads:[~2026-08-14 23:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 23:48 Joshua Washington [this message]
2026-08-14 23:48 ` [PATCH net 1/6] gve: increment work_done for XDP and error packets Joshua Washington
2026-08-14 23:48 ` [PATCH net 2/6] gve: fix XSK buffer leak when rings are stopped Joshua Washington
2026-08-14 23:48 ` [PATCH net 3/6] gve: fix XSK buffer leak on error descriptor Joshua Washington
2026-08-14 23:48 ` [PATCH net 4/6] gve: don't register xsk pool on pre-existing queues in RDA mode Joshua Washington
2026-08-14 23:48 ` [PATCH net 5/6] gve: fix napi_disable deadlock when attempting to disable XSK pools Joshua Washington
2026-08-14 23:48 ` [PATCH net 6/6] gve: fix NULL dereference from premature XSK pool DMA unmap Joshua Washington
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=20260814234845.773189-1-joshwash@google.com \
--to=joshwash@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=jordanrhee@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nktgrg@google.com \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=sdf@fomichev.me \
--cc=thostet@google.com \
--cc=willemb@google.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