This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Question about EI_ABIVERSION handling
- From: Florian Weimer <fweimer at redhat dot com>
- To: Dragan Mladjenovic <dmladjenovic at wavecomp dot com>
- Cc: "libc-alpha\@sourceware.org" <libc-alpha at sourceware dot org>, "joseph\@codesourcery.com" <joseph at codesourcery dot com>, "Maciej W . Rozycki" <macro at linux-mips dot org>, Alan Modra <amodra at gmail dot com>, Carlos O'Donell <carlos at redhat dot com>, Faraz Shahbazker <fshahbazker at wavecomp dot com>
- Date: Wed, 26 Jun 2019 14:01:41 +0200
- Subject: Re: Question about EI_ABIVERSION handling
- References: <CY4PR22MB011905F40D52E703EB0F121CB3E20@CY4PR22MB0119.namprd22.prod.outlook.com>
* Dragan Mladjenovic:
> It seems that ld.so does not validate EI_ABIVERSION of main executable
> when the said executable is loaded directly by the kernel.
Hmm. I think this may be an oversight. I can confirm this behavior on
x86-64.
> Is this behavior intended? If I would wish to ensure that executable
> with newer ABI version get rejected by the old loaders, am I expected
> to add some other incompatible change like new dynamic tag?
Unknown dynamic tags are ignored (like unknown program headers). Only
unknown relocation types result in errors.
Thanks,
Florian