mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <>
To: Florian Weimer <>
Cc: Nihal Jere <>,
Subject: Re: [musl] Dynamic linker segfault
Date: Wed, 5 Jan 2022 08:49:58 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Jan 05, 2022 at 09:56:25AM +0100, Florian Weimer wrote:
> * Rich Felker:
> > This is a malformed program file not compatible with the machine page
> > size (4k). Arguably it should be detected as p_align < PAGESIZE -- in
> > a sense, p_align for LOAD segments is the maximum supported page size
> > for the program file, and machines not capable of providing a page
> > size that small can't map/run it. In theory the loader could allow
> > this if all the differences between segments satisfy the right
> > congruences and have matching permissions where the maps would
> > overlap, but I'm not sure that's useful.
> We've been looking at this on the glibc side recently.  The use case is
> supporting large data alignments (greater than the kernel page size)
> while not pessimizing multi-page-size targets such as POWER and AArch64.

I'm not clear how it pessimizes these targets (beyond what's
fundamentally necessary) unless you're artificially aligning segment
contents on disk to a large alignment boundary to prevent over-mapping
(undermining separate-code for example). And if you're doing that, you
need the full alignment anyway to support machines with larger
hardware pagesize. Otherwise you'd get back the overmapping (and
unwanted perission exposure).

The only other thing I can think of is pessimizing ASLR by requiring
more alignment (throwing away a few bits of position entropy).

In any case, do you know if this test file is somehow related to that
work, or is it just a guess? It doesn't seem to be related to me since
it's essentially a "pageless" mapping setup.


  reply	other threads:[~2022-01-05 13:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 21:27 Nihal Jere
2022-01-04 21:42 ` Rich Felker
2022-01-05  8:56   ` Florian Weimer
2022-01-05 13:49     ` Rich Felker [this message]
2022-01-05 14:00       ` Florian Weimer
2022-01-05 15:00         ` Rich Felker
2022-01-07 13:58           ` Florian Weimer
2022-01-07 17:35             ` Rich Felker
2022-01-10 13:30               ` Florian Weimer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).