Your message dated Wed, 8 Feb 2012 12:52:49 +0100
with message-id <[email protected]>
and subject line Re: Bug#658278: ld.so segfaults on wrong input
has caused the Debian Bug report #658278,
regarding ld.so segfaults on wrong input
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
658278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658278
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libc6
Version: 2.13-21
Severity: normal
File: /lib64/ld-linux-x86-64.so.2

Running ld.so with the wrong kind of file segfaults:

mrvn@frosties:~% /lib64/ld-linux-x86-64.so.2 /usr/lib/klibc/bin/ls 
zsh: segmentation fault  /lib64/ld-linux-x86-64.so.2 /usr/lib/klibc/bin/ls

MfG
        Goswin

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6 depends on:
ii  libc-bin  2.13-21  
ii  libgcc1   1:4.6.2-5

libc6 recommends no packages.

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.41 
ii  glibc-doc              <none> 
ii  locales                2.13-21

-- debconf information excluded



--- End Message ---
--- Begin Message ---
On Wed, Feb 08, 2012 at 11:02:12AM +0100, Goswin von Brederlow wrote:
> reopen 658278
> thanks
> 
> Aurelien Jarno <[email protected]> writes:
> 
> > On Wed, Feb 01, 2012 at 07:47:29PM +0100, Goswin von Brederlow wrote:
> >> Package: libc6
> >> Version: 2.13-21
> >> Severity: normal
> >> File: /lib64/ld-linux-x86-64.so.2
> >> 
> >> Running ld.so with the wrong kind of file segfaults:
> >> 
> >> mrvn@frosties:~% /lib64/ld-linux-x86-64.so.2 /usr/lib/klibc/bin/ls 
> >> zsh: segmentation fault  /lib64/ld-linux-x86-64.so.2 /usr/lib/klibc/bin/ls
> >> 
> >
> > It's not the wrong file type:
> >
> > $file /usr/lib/klibc/bin/ls
> > /usr/lib/klibc/bin/ls: ELF 64-bit LSB executable, x86-64, version 1
> > (SYSV), statically linked (uses shared libs), stripped
> >
> > It's an ELF file, but given it has a different ABI just doesn't work
> > with /lib64/ld-linux-x86-64.so.2. It's hardly the fault of the libc.
> 
> It has a different interpreter in its elf section. Ld.so could check
> that to determine wether the elf file is one it should care about.

No, if you execute it calling /lib64/ld-linux-x86-64.so.2 $program, it's
actually to override the entry in ld.so. The interpreter in the ELF
entry is there to let the kernel know which interpreter it should
invoke, not to do comparison. Doing so would have prevented fixing the
ELF interpreter on amd64, or doing the transition from one interpreter
to another on armhf, and users would had needed to reinstall there
system instead of doing an upgrade. Definitely not something we need.

> A segfault is never correct behaviour and needs to be fixed in ld.so.
> 

It is nothing different than a user replacing a library by another with
the same name but with a different ABI. It segfaults because the ABI is
incompatible, ie different number or type of parameters in functions.
The fact that it happens in ld.so or in another library doesn't matter
here.

So there is no bug, I am therefore closing it.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
[email protected]                 http://www.aurel32.net


--- End Message ---

Reply via email to