From: Harshitha Ramamurthy <hramamurthy@google.com>
To: netdev@vger.kernel.org
Cc: joshwash@google.com, hramamurthy@google.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com,
thostet@google.com, jordanrhee@google.com, ziweixiao@google.com,
willemb@google.com, nktgrg@google.com, pkaligineedi@google.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [PATCH net 0/2] gve: Bug fixes for header-split and PTP
Date: Fri, 7 Aug 2026 22:43:13 +0000 [thread overview]
Message-ID: <20260807224315.234152-1-hramamurthy@google.com> (raw)
This series contains 2 bug fixes for gve.
Patch 1 fixes an issue which causes TX timeouts due to HW detection of
an illegal descriptor. This happens when receiving header-only packets
with header split enabled - this produces an SKB with a zero-length
fragment.
Patch 2 prevents a kernel NULL pointer dereference by stubbing the PTP
adjfine callback.
Jordan Rhee (2):
gve: fix zero-length skb frag with header-split
gve: fix NULL dereference due to missing ptp adjfine
drivers/net/ethernet/google/gve/gve_ptp.c | 6 ++++++
drivers/net/ethernet/google/gve/gve_rx_dqo.c | 5 +++++
2 files changed, 11 insertions(+)
--
2.55.0.679.g6767b8d81c-goog
next reply other threads:[~2026-08-07 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 22:43 Harshitha Ramamurthy [this message]
2026-08-07 22:43 ` [PATCH net 1/2] gve: fix zero-length skb frag with header-split Harshitha Ramamurthy
2026-08-07 22:43 ` [PATCH net 2/2] gve: fix NULL dereference due to missing ptp adjfine Harshitha Ramamurthy
2026-08-08 15:26 ` Vadim Fedorenko
2026-08-10 15:55 ` Jordan Rhee
2026-08-10 16:15 ` Vadim Fedorenko
2026-08-12 1:30 ` [PATCH net 0/2] gve: Bug fixes for header-split and PTP patchwork-bot+netdevbpf
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=20260807224315.234152-1-hramamurthy@google.com \
--to=hramamurthy@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jordanrhee@google.com \
--cc=joshwash@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=richardcochran@gmail.com \
--cc=stable@vger.kernel.org \
--cc=thostet@google.com \
--cc=willemb@google.com \
--cc=ziweixiao@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
all inboxes | Powered by JetHome®