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: [PATCH] [BZ #14579] rtld: limit the self loading check to normalmode


On 9/14/2012 1:11 PM, Roland McGrath wrote:
>> Agreed, it's wrong that `./elf/ld.so --verify ./elf/ld-linux-x86-64.so.2`
>> returns an exit status of 127, it should IMO return 1 indicating that
>> it is *not* a "dynamically linked object we can handle" (it's a statically
>> linked object).
> 
> Actually, it's a dynamically linked object that has no dependencies.
> I don't know why we shouldn't be able to handle it.

Is having a dynamic section the only qualifier for being labelled as a dynamically
inked object? Conceptually I've always been calling the dynamic linker "statically
linked", but I know that such a name is neither correct nor precise.

I agree that we *should* be able to handle it, but I don't know that we can
call it a "dynamically linked object we can handle." I don't know that we can
chain-load from one loader to another. I would expect it to work, but purely
at a theoretical level.
 
>> Does your patch cause ld.so --verify to return 1 as it does for statically
>> linked binaries?
> 
> It returns 2, but --list says "statically linked".
 
Would be nice if it return 1 and said "dyanmic loader".

Cheers,
Carlos.
-- 
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026


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