public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Cc: Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH v2] elf: Implement filtering of symbols historically defined in libpthread
Date: Wed, 5 May 2021 11:10:02 -0300	[thread overview]
Message-ID: <9a5b4cec-15e6-8c89-9d01-1f2d78deb804@linaro.org> (raw)
In-Reply-To: <87eeelfg77.fsf@oldenburg.str.redhat.com>



On 05/05/2021 10:44, Florian Weimer via Libc-alpha wrote:
> Definitions of these symbols in libc expose bugs in existing binaries
> linked against earlier glibc versions.  Therefore, hide these symbols
> for old binaries.
> 
> The symbol list in sysdeps/nptl/dl-pthread-weak.c contains some
> symbols which have not been moved yet, but that is harmless because
> the function is only invoked if the symbol is found in libc.so.
Can we postpone this fix until we get all the symbols from libpthread
properly moved? I really dislike the symbol filter list, it is error
prone and add unnecessary code size.

  reply	other threads:[~2021-05-05 14:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-05 13:44 Florian Weimer
2021-05-05 14:10 ` Adhemerval Zanella [this message]
2021-05-05 15:30   ` Florian Weimer
2021-05-05 15:53   ` H.J. Lu
2021-05-05 16:01     ` Florian Weimer
2021-05-05 16:55       ` Adhemerval Zanella
2021-05-05 17:19         ` Florian Weimer
2021-05-05 17:52           ` H.J. Lu
2021-05-05 17:56             ` Florian Weimer
2021-05-05 18:06           ` Adhemerval Zanella
2021-05-05 18:16             ` Florian Weimer
2021-05-05 18:18               ` H.J. Lu
2021-05-05 18:28                 ` Florian Weimer
2021-05-05 18:30                   ` H.J. Lu
2021-05-05 18:48                     ` Florian Weimer
2021-05-05 18:50                       ` H.J. Lu
2021-05-05 19:08                         ` Florian Weimer
2021-05-05 19:32                           ` H.J. Lu
2021-05-05 19:53                             ` Florian Weimer
2021-05-05 19:03 ` Andreas Schwab
2021-05-05 19:10   ` Florian Weimer
2021-05-05 20:48     ` H.J. Lu
2021-05-05 20:53       ` H.J. Lu
2021-05-06  9:17         ` Florian Weimer
2021-05-06 12:08           ` H.J. Lu
2021-05-06 12:50             ` Florian Weimer
2021-05-06 12:58               ` Adhemerval Zanella
2021-05-06 13:15               ` H.J. Lu
2021-05-07 14:46 ` Florian Weimer
2021-05-07 16:40   ` H.J. Lu
2021-05-10 13:48     ` Florian Weimer
2021-05-10 14:02       ` H.J. Lu
2021-05-10 14:08         ` Florian Weimer
2021-05-11  0:04           ` H.J. Lu

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=9a5b4cec-15e6-8c89-9d01-1f2d78deb804@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@linux-m68k.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).