This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Encoding page size in the ELF header


On 25/09/15 14:04, Florian Weimer wrote:
Not sure if this the right mailing list for this discussion.

I think we should record the expected page size in the ELF header in
some way.  It affects the behavior of the static linker, the dynamic
linker, and even some applications.  (For example, an application might
want to make a part of .data read-only after initialization, as a
hardening measure.)


you mean to fail when the runtime page size does
not match the expected page size of the binary?
(that would make binaries non-portable so each
page size would be a different abi).

or do you want a hint that makes things more
efficient/secure in the normal case, but there
is still some fall back?
(i'm not sure how this could work)

What would be a good way to do that?



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]