public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/28857] FAIL: elf/tst-audit24a
Date: Sat, 05 Feb 2022 23:29:43 +0000	[thread overview]
Message-ID: <bug-28857-131-sivbQaMAlZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28857-131@http.sourceware.org/bugzilla/>

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

--- Comment #5 from dave.anglin at bell dot net ---
On 2022-02-04 1:53 p.m., adhemerval.zanella at linaro dot org wrote:
> The _dl_lookup_address seems to be indeed required and I also think we should
> only updated the binding if la_symbind actually acts uppon it.  The following
> patch fixes the tests on hppa:
Attached is an updated patch.  The change to DL_FIXUP_BINDNOW_RELOC was not
correct.
As far as I can tell, it is not necessary to call _dl_lookup_address.  But we
do need to clear the
plabel bit from new_value or st_value.  I think the same issue could also
potentially occur with
DL_FIXUP_ADDR_VALUE.

I also hacked things a bit to fix warning from dl-fptr.c.

I'm still not sure where the nameless R_PARISC_IPLT relocation comes from.

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

  parent reply	other threads:[~2022-02-05 23:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 14:25 [Bug libc/28857] New: " danglin at gcc dot gnu.org
2022-02-03 20:17 ` [Bug libc/28857] " adhemerval.zanella at linaro dot org
2022-02-03 20:49 ` dave.anglin at bell dot net
2022-02-04 18:53 ` adhemerval.zanella at linaro dot org
2022-02-05  0:33 ` dave.anglin at bell dot net
2022-02-05 23:29 ` dave.anglin at bell dot net [this message]
2022-02-07 12:11 ` adhemerval.zanella at linaro dot org
2022-02-07 12:50 ` adhemerval.zanella at linaro dot org
2022-02-07 15:16 ` dave.anglin at bell dot net
2022-02-09 12:13 ` adhemerval.zanella at linaro dot org
2023-01-17 18:57 ` sam at gentoo dot org

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-28857-131-sivbQaMAlZ@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).