From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Andries.Brouwer@cwi.nl
Cc: szepe@pinerecords.com, torvalds@osdl.org,
linux-kernel@vger.kernel.org, root@chaos.analogic.com
Subject: Re: BUG (non-kernel), can hurt developers.
Date: Fri, 28 Nov 2003 12:22:38 -0500 [thread overview]
Message-ID: <3FC7845E.1080800@nortelnetworks.com> (raw)
In-Reply-To: UTC200311281029.hASATvD16681.aeb@smtp.cwi.nl
Andries.Brouwer@cwi.nl wrote:
> The routine handler must be very careful, since processing
> elsewhere was interrupted at some arbitrary point. POSIX
> has the concept of "safe function". If a signal inter
> rupts an unsafe function, and handler calls an unsafe
> function, then the behavior is undefined. Safe functions
> are listed explicitly in the various standards. The POSIX
> 1003.1-2003 list is
<snip>
You may also want to mention the SUS async-safe list as well, since
there are some additional functions there.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-11-28 17:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 10:29 BUG (non-kernel), can hurt developers Andries.Brouwer
2003-11-28 17:22 ` Chris Friesen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-28 21:21 Andries.Brouwer
2003-11-28 21:38 ` Chris Friesen
2003-11-26 16:54 Richard B. Johnson
2003-11-26 17:21 ` YOSHIFUJI Hideaki / 吉藤英明
2003-11-26 18:29 ` Linus Torvalds
2003-11-26 18:55 ` Richard B. Johnson
2003-11-26 19:33 ` Jamie Lokier
2003-11-26 20:17 ` Richard B. Johnson
2003-11-26 20:42 ` Jamie Lokier
2003-11-26 18:59 ` YOSHIFUJI Hideaki / 吉藤英明
2003-11-27 20:41 ` Mikulas Patocka
2003-11-28 7:18 ` Tomas Szepe
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=3FC7845E.1080800@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=szepe@pinerecords.com \
--cc=torvalds@osdl.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 NNTP newsgroup(s).