Messages in this thread | | | Subject | Re: Lack of Documentation about SA_RESTART... | From | Philippe Troin <> | Date | 11 Jul 2005 20:30:20 -0700 |
| |
"Theodore Ts'o" <tytso@mit.edu> writes:
> On Mon, Jul 11, 2005 at 12:32:37PM +0200, Paolo Ornati wrote: > > But what I'm looking for is a list of syscalls that are automatically > > restarted when SA_RESTART is set, and especially in what conditions. > > > > For example: read(), write(), open() are obviously restarted, but even > > on non-blocking fd? > > And what about connect() and select() for example? > > > > There are a lot of syscalls that can fail with "EINTR"! What's the > > advantage of using SA_RESTART if one doesn't know what syscalls are > > restarted? > > According to the Single Unix Specification V3, all functions that > return EINTR are supposed to restart if a process receives a signal > where signal handler has been installed with the SA_RESTART flag.
Except for select() and poll(), which should always return EINTR even when interrupted with a SA_RESTART signal.
Phil. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |