linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: hev <r@hev.cc>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Kees Cook <kees@kernel.org>,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] binfmt_elf: Align eligible read-only PT_LOAD segments to PMD_SIZE for THP
Date: Tue, 3 Mar 2026 05:32:51 +0000	[thread overview]
Message-ID: <aaZyg0GT4_f52UEr@casper.infradead.org> (raw)
In-Reply-To: <CAHirt9j-appZ+Mn=8AoG=SW3Lrqi2ajdZDGp8yYWiBWkzBbQ9g@mail.gmail.com>

On Tue, Mar 03, 2026 at 12:31:59PM +0800, hev wrote:
> On Tue, Mar 3, 2026 at 12:46 AM Matthew Wilcox <willy@infradead.org> wrote:
> >
> > On Mon, Mar 02, 2026 at 11:50:46PM +0800, WANG Rui wrote:
> > > +config ELF_RO_LOAD_THP_ALIGNMENT
> > > +     bool "Align read-only ELF load segments for THP (EXPERIMENTAL)"
> > > +     depends on READ_ONLY_THP_FOR_FS
> >
> > This doesn't deserve a config option.
> 
> This optimization is not entirely free. Increasing PT_LOAD alignment
> can waste virtual address space, which is especially significant on
> 32-bit systems, and it also reduces ASLR entropy by limiting the
> number of possible load addresses.
> 
> In addition, coarser alignment may have secondary microarchitectural
> effects (eg. on indirect branch prediction), depending on the
> workload. Because this change affects address space layout and
> security-related properties, providing users with a way to opt out is
> reasonable, rather than making it completely unconditional. This
> behavior fits naturally under READ_ONLY_THP_FOR_FS.

This isn't reasonable at all.  You're asking distro maintainers to make
a decision they have insufficient information to make.  Almost none of
our users compile their own kernels, and frankly those that do don't have
enough information to make an informed decision about which way to choose.

So if we're going to have a way to opt in/out, it needs to be something
different.  Maybe a heuristic based on size of text segment?  Maybe an
ELF flag?  But then, if we're going to modify the binary, why not just
set p_align and then we don't need this patch at all?


  reply	other threads:[~2026-03-03  5:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 15:50 WANG Rui
2026-03-02 16:45 ` Matthew Wilcox
2026-03-03  4:31   ` hev
2026-03-03  5:32     ` Matthew Wilcox [this message]
2026-03-03  7:00       ` hev

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=aaZyg0GT4_f52UEr@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=kees@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=r@hev.cc \
    --cc=viro@zeniv.linux.org.uk \
    /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