From: Kurt Roeckx <Q@ping.be>
To: Dawson Engler <engler@csl.Stanford.EDU>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [QUESTION] which routines must be re-entrant?
Date: Fri, 1 Jun 2001 17:37:45 +0200 [thread overview]
Message-ID: <20010601173745.A421@ping.be> (raw)
In-Reply-To: <200105312301.QAA16524@csl.Stanford.EDU>
In-Reply-To: <200105312301.QAA16524@csl.Stanford.EDU>
On Thu, May 31, 2001 at 04:01:34PM -0700, Dawson Engler wrote:
> Is there an easy way to tell which routines must be re-entrant?
> (it doesn't have to be exhaustive, even an incomplete set is useful)
>
> I was going to write a checker to make sure supposedly re-entrant
> routines actually were, but was having a hard time figuring out which
> ones were supposed to be...
Their was an post on bugtraq a few days ago about this, it had a
list with all system calls which are reentrant safe under
OpenBSD. The paper was about signals, and is available at
http://razor.bindview.com/publish/papers/signals.txt
OpenBSD had a manpage wich lists all the function which should be
be safe to call from a signal handler. It might be a nice
place to start. You should only look at those from section 2
of course.
http://www.openbsd.org/cgi-bin/man.cgi?query=sigaction
Kurt
prev parent reply other threads:[~2001-06-01 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 23:01 [QUESTION] which routines must be re-entrant? Dawson Engler
2001-06-01 15:37 ` Kurt Roeckx [this message]
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=20010601173745.A421@ping.be \
--to=q@ping.be \
--cc=engler@csl.Stanford.EDU \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.