From: Jakub Kicinski <kuba@kernel.org>
To: Joshua Washington <joshwash@google.com>
Cc: netdev@vger.kernel.org,
Harshitha Ramamurthy <hramamurthy@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemb@google.com>,
Ankit Garg <nktgrg@google.com>,
Praveen Kaligineedi <pkaligineedi@google.com>,
Catherine Sullivan <csully@google.com>,
Luigi Rizzo <lrizzo@google.com>, Jon Olson <jonolson@google.com>,
Sagi Shahar <sagis@google.com>, Bailey Forrest <bcf@google.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net 0/2] gve: fix crashes on invalid TX queue indices
Date: Tue, 6 Jan 2026 18:22:44 -0800 [thread overview]
Message-ID: <20260106182244.7188a8f6@kernel.org> (raw)
In-Reply-To: <20260105232504.3791806-1-joshwash@google.com>
On Mon, 5 Jan 2026 15:25:02 -0800 Joshua Washington wrote:
> This series fixes a kernel panic in the GVE driver caused by
> out-of-bounds array access when the network stack provides an invalid
> TX queue index.
Do you know how? I seem to recall we had such issues due to bugs
in the qdisc layer, most of which were fixed.
Fixing this at the source, if possible, would be far preferable
to sprinkling this condition to all the drivers.
next prev parent reply other threads:[~2026-01-07 2:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 23:25 [PATCH net 0/2] gve: fix crashes on invalid TX queue indices Joshua Washington
2026-01-05 23:25 ` [PATCH net 1/2] gve: drop packets on invalid queue indices in GQI TX path Joshua Washington
2026-01-05 23:25 ` [PATCH net 2/2] gve: drop packets on invalid queue indices in DQO " Joshua Washington
2026-01-07 2:22 ` Jakub Kicinski [this message]
2026-01-08 15:35 ` [PATCH net 0/2] gve: fix crashes on invalid TX queue indices Ankit Garg
2026-01-08 16:31 ` Jakub Kicinski
2026-01-08 16:37 ` Eric Dumazet
2026-01-08 20:53 ` Ankit Garg
2026-01-30 20:56 ` Eric Dumazet
2026-01-31 0:38 ` Jakub Kicinski
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=20260106182244.7188a8f6@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcf@google.com \
--cc=csully@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jonolson@google.com \
--cc=joshwash@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrizzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=nktgrg@google.com \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=sagis@google.com \
--cc=stable@vger.kernel.org \
--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