public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: ld.so needs __errno_location PLT entry?
Date: Sun, 29 Sep 2002 15:41:00 -0000	[thread overview]
Message-ID: <200209292235.g8TMZx420266@magilla.sf.frob.com> (raw)

Unless I am missing something, I think ld.so needs to have a PLT entry for
__errno_location.  This bites fatally on Hurd, where the implementations of
read et al must come from libc.so and so the real errno must be found by
ld.so's calls to see any values at all.  On Linux with PLT reduction it
never matters to communicate an errno value between libc and ld.so, so
always getting ld.so's private errno cell is fine most of the time.  But
there is only one private cell, so ld.so's uses of it are not thread-safe.
I am not positive off hand that every possible access to errno inside ld.so
happens with _dl_load_lock held.  If so, then it's ok.  But that is
certainly a subtlety that requires some comments somewhere.

                 reply	other threads:[~2002-09-29 22:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200209292235.g8TMZx420266@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    /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).