public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/29235] Some tests crash in ELF_DYNAMIC_DO_RELR on powerpc64le
Date: Thu, 09 Jun 2022 10:38:43 +0000	[thread overview]
Message-ID: <bug-29235-131-X7ixdLISg8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29235-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29235

--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
With hard-coded paths in tests, I get:

(gdb) print where
$3 = (Elf64_Addr *) 0x100255db8

which is in this read-only mapping:

100160000-100260000 r--p 00160000 08:03 2153963751                      
/builddir/build/BUILD/glibc-2.35.9000-583-gace9e3edbc/build-2/math/test-tgmath3-fma

0000000000255db8 appears in readelf -rW output, so I don't think ld.so's RELR
implementation is at fault.

It looks like page size issue, and the DT_RELR may be accidental. The system
has 64K pages, but we have for the main executable:

  LOAD           0x160000 0x0000000000160000 0x0000000000160000 0x0f10a4
0x0f10a4 R   0x10000
  LOAD           0x255db0 0x0000000000265db0 0x0000000000265db0 0x06a40c
0x06a988 RW  0x10000
[…]
  GNU_RELRO      0x255db0 0x0000000000265db0 0x0000000000265db0 0x06a250
0x06a250 R   0x1

I'm not sure if this kind of layout is supposed to work with 64K pages. Note
that as discussed elsewhere, ld.so rounds down 0x255db0 to the next multiple of
65,536.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-06-09 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 10:19 [Bug dynamic-link/29235] New: " fweimer at redhat dot com
2022-06-09 10:19 ` [Bug dynamic-link/29235] " fweimer at redhat dot com
2022-06-09 10:38 ` fweimer at redhat dot com [this message]
2022-06-09 10:41 ` fweimer at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29235-131-X7ixdLISg8@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).