From: Kees Cook <kees@kernel.org>
To: Eric Dumazet <edumazet@google.com>,
Pranav Tyagi <pranav.tyagi03@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
andrew+netdev@lunn.ch, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] net: randomize layout of struct net_device
Date: Fri, 06 Jun 2025 12:46:10 -0700 [thread overview]
Message-ID: <123565BC-9619-40F1-9F38-0F2BAAE09716@kernel.org> (raw)
In-Reply-To: <CANn89iJR1i3hhXrkDNtXyPCNUj1KmrTAff2=pcuYNsXBxogNpw@mail.gmail.com>
On June 6, 2025 8:42:45 AM PDT, Eric Dumazet <edumazet@google.com> wrote:
>Most distros use CONFIG_RANDSTRUCT_NONE=y
That is true. But distros don't strictly define our code base. :)
> I do not think __randomize_layout has a future.
It will remain an actively supported feature -- many high security systems (that build their own kernels) use it, along with other features where they have no problem trading performance for security.
-Kees
--
Kees Cook
prev parent reply other threads:[~2025-06-06 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 13:59 [PATCH] net: randomize layout of struct net_device Pranav Tyagi
2025-06-02 14:07 ` Kees Cook
2025-06-02 14:22 ` Pranav Tyagi
2025-06-02 14:43 ` Pranav Tyagi
2025-06-02 14:07 ` Greg KH
2025-06-06 15:04 ` Pranav Tyagi
2025-06-02 14:46 ` Andrew Lunn
2025-06-02 18:03 ` Kees Cook
2025-06-02 19:06 ` Andrew Lunn
2025-06-06 14:55 ` Pranav Tyagi
2025-06-06 15:42 ` Eric Dumazet
2025-06-06 19:46 ` 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=123565BC-9619-40F1-9F38-0F2BAAE09716@kernel.org \
--to=kees@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pranav.tyagi03@gmail.com \
--cc=skhan@linuxfoundation.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