svn commit: r339876 - head/libexec/rtld-elf

[Konstantin Belousov]

On Fri, Nov 02, 2018 at 05:51:25PM -0700, Mark Millard wrote:
> On 2018-Nov-2, at 11:50 AM, Konstantin Belousov <kostikbel at gmail.com> wrote:
> 
> > On Fri, Nov 02, 2018 at 10:38:08AM -0700, Mark Millard wrote:
> >> . . .
> > 
> > There seems to be an issue with the direct execution mode on ppc.
> > Even otherwise working ld-elf.so.1 segfaults if I try to use it as
> > standalone binary.
> > 
> > But if I specify patched ld-elf.so.1 as the interpreter for some program,
> > using 'cc -Wl,-I,<path>/ld-elf.so.1' it works.  So I see there two bugs,
> > one is regression due to textsize calculation, which should be fixed by
> > my patch.  Another is the direct exec problem.
> 
> My head -r339076 based powerpc64 and armv7 contexts also
> fail for:
> 
> # /libexec/ld-elf.so.1 /bin/ls
> 
> The armv7 (a Cortext-A7 context) is interestingly different
> in how it fails:
> 
> # /libexec/ld-elf.so.1 /bin/ls
> ld-elf.so.1: /bin/ls: mmap of entire address space failed: Cannot allocate memory
Can you show the ktrace/kdump for this ?

> 
> My aarch64 context (a Cortext-A53 context) had no problem.
> 
> (All 3 examples are without any of the the recent updates
> or patches to ld-elf.so.1 source code.)

And still, does the patch for isync range works ?  You can test the new
ld-elf.so.1 standalone by hard-coding its path into the binary.  Build e.g.
only ls(1) by using make in its directory, then re-issue the linking
command with the additional flag '-Wl,-I,<path to patched ld-elf.so.1>
and try to run ls.full.