From: David Mosberger <davidm@napali.hpl.hp.com>
To: Roland McGrath <roland@redhat.com>
Cc: davidm@hpl.hp.com, libc-hacker@sources.redhat.com
Subject: Re: is dl_iterate_phdr() supposed to be async-signal safe?
Date: Fri, 02 Apr 2004 00:09:00 -0000 [thread overview]
Message-ID: <16492.44824.546092.273252@napali.hpl.hp.com> (raw)
In-Reply-To: <200404012122.i31LM3sg027149@magilla.sf.frob.com>
>>>>> On Thu, 1 Apr 2004 13:22:03 -0800, Roland McGrath <roland@redhat.com> said:
Roland> Why would you have thought that it was? It is
Roland> well-specified that no interface is async-signal-safe unless
Roland> explicitly listed as such. No such claim was ever made
Roland> about dl_iterate_phdr.
Because otherwise there is no way to unwind from a signal handler and
I was mislead by the fact that it was using a recursive lock (and it
was only indirectly calling pthread_mutex_lock(), which is defined not
to be async-signal safe).
Can this please be fixed? Wouldn't it be sufficient to disable signal
delivery during lock acquisition/release and while modifying the ELF
object list?
--david
next prev parent reply other threads:[~2004-04-02 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 7:50 David Mosberger
2004-04-01 21:22 ` Roland McGrath
2004-04-02 0:09 ` David Mosberger [this message]
2004-04-19 18:39 ` what to do about dl_iterate_phdr() David Mosberger
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=16492.44824.546092.273252@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davidm@hpl.hp.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@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).