[lkml]   [2005]   [Jul]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Lack of Documentation about SA_RESTART...
On Sun, 24 Jul 2005 10:56:08 -0400
Theodore Ts'o <> wrote:

> The spect says "unless otherwise specified". The description for
> pause() states that the process will sleep until receiving a signal
> that terminates the process or causes it to call signal-handling
> function. That would presumably count as an "otherwise specified".

I don't think that way for at least 2 reasons:

1) SA_RESTART is an XSI extension, so every exception to the rule
"everything automatically restarted" should be under an XSI section
(like it is on the "select()" page).

2) The same thing that you claim for "pause()" (that isn't restarted)
can be claimed for other syscalls that _ARE_ restarted.

Example: wait()

SUSV3 DOC: "... The wait() function shall suspend execution of the
calling thread until status information for one of the terminated child
processes of the calling process is available, or until delivery of a
signal whose action is either to execute a signal-catching function or
to terminate the process ..."

And wait() is actually RESTARTED because:

- it makes sense
- FreeBSD sigaction() mapage says it is retarted

- Linux does it (see kernel/exit.c)

retval = -ERESTARTSYS;
if (signal_pending(current))
goto end;


Paolo Ornati
Linux 2.6.13-rc3 on x86_64
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-07-25 10:07    [W:0.045 / U:2.856 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site