From: Kees Cook <kees@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Qingfang Deng <qingfang.deng@linux.dev>,
Jiri Pirko <jiri@resnulli.us>,
Brad Spengler <spender@grsecurity.net>,
PaX Team <pageexec@gmail.com>, Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-hardening@vger.kernel.org,
Yeswanth Krishna Tellakula <yeswanth@linux.ibm.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next net] netdev: Hide the netdev_priv() origin from GCC in netdev_from_priv()
Date: Thu, 15 Oct 2026 10:58:26 -0700 [thread overview]
Message-ID: <202610151056.DB82177C@keescook> (raw)
In-Reply-To: <20261015103410.15ae1b8e@kernel.org>
On Thu, Oct 15, 2026 at 10:34:10AM -0700, Jakub Kicinski wrote:
> On Thu, 15 Oct 2026 10:07:06 -0700 Kees Cook wrote:
> > geh, for the subject "net" and "net-next" glitch: I've poked my
> > subject-building tooling again, this should be for "net", not
> > "net-next"...
>
> :) Ack. Just missed today's PR but looks like this is 2 releases
> old so not _extremely_ urgent. If you think it is we can also ask
> Linus to take it direct
This is only hitting one place (currently), but as it went unnoticed for
a while (GCC has been bugged for a few releases, it seems), I think the
urgency isn't high.
--
Kees Cook
prev parent reply other threads:[~2026-10-15 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 17:00 [PATCH net-next net] netdev: Hide the netdev_priv() origin from GCC in netdev_from_priv() Kees Cook
2026-10-15 17:07 ` Kees Cook
2026-10-15 17:34 ` Jakub Kicinski
2026-10-15 17:58 ` Kees Cook [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=202610151056.DB82177C@keescook \
--to=kees@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=justinstitt@google.com \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=morbo@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pageexec@gmail.com \
--cc=qingfang.deng@linux.dev \
--cc=spender@grsecurity.net \
--cc=stable@vger.kernel.org \
--cc=yeswanth@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.