[lkml]   [2005]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Lack of Documentation about SA_RESTART...
    "Theodore Ts'o" <> 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.

    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-12 05:34    [W:0.019 / U:9.512 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site