From: Mark Lord <lkml@rtr.ca>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Michael Kerrisk <mtk-lkml@gmx.net>,
raa.lkml@gmail.com, trond.myklebust@fys.uio.no, boi@boi.at,
linux-kernel@vger.kernel.org
Subject: Re: blocking file lock functions (lockf,flock,fcntl) do not return after timer signal
Date: Wed, 12 Oct 2005 12:06:43 -0400 [thread overview]
Message-ID: <434D3493.8020304@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.61.0510121138450.4391@chaos.analogic.com>
linux-os (Dick Johnson) wrote:
> On Wed, 12 Oct 2005, Michael Kerrisk wrote:
>
>>But this is not correct. write() is async-signal-safe (POSIX
>>requires it).
>
> Then tell it to the doom-sayers who always excoriate me when
> I use a 'C' runtime library call in test signal code. I have
> been told that the __only__ thing you can do in a signal handler
> is access global memory and/or execute siglongjmp().
Try "man 2 signal", and read the list of signal-safe functions
given at the bottom of the manpage, from POSIX 1003.1-2003.
write() is included (of course it is, since it is really a
kernel syscall not a library function).
Cheers
next prev parent reply other threads:[~2005-10-12 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 7:54 blocking file lock functions (lockf,flock,fcntl) do not return after timer signal "Dieter Müller (BOI GmbH)"
2005-10-12 12:48 ` Alex Riesen
2005-10-12 13:09 ` linux-os (Dick Johnson)
2005-10-12 14:39 ` Trond Myklebust
2005-10-12 15:10 ` Alex Riesen
2005-10-12 15:20 ` linux-os (Dick Johnson)
2005-10-12 15:37 ` Michael Kerrisk
2005-10-12 15:43 ` linux-os (Dick Johnson)
2005-10-12 16:05 ` Michael Kerrisk
2005-10-12 16:06 ` Mark Lord [this message]
2005-10-12 21:15 ` Alex Riesen
2005-10-12 16:36 ` Trond Myklebust
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=434D3493.8020304@rtr.ca \
--to=lkml@rtr.ca \
--cc=boi@boi.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=mtk-lkml@gmx.net \
--cc=raa.lkml@gmail.com \
--cc=trond.myklebust@fys.uio.no \
/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