linux-kernel - Re: pselect semantics - no EINTR with pending signals

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 11 Sep 2011 10:45:45 -0400
From:	Ulrich Drepper <drepper@...il.com>
To:	Maciek Borzecki <maciek.borzecki@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: pselect semantics - no EINTR with pending signals

On Fri, Sep 9, 2011 at 09:25, Maciek Borzecki <maciek.borzecki@...il.com> wrote:
> Now, I'm not sure about the semantics of pselect. I'm not saying that
> the current version is right or wrong, but raising a question if this
> is really expected (and it did happen to be quite unexpected for me).

The standard says

       If  sigmask  is not a null pointer, then the pselect() function
shall replace the signal mask of the
       process by the set of signals pointed to by sigmask before
examining  the  descriptors,  and  shall
       restore the signal mask of the process before returning.

The way I read this the kernel does have to give the signal a chance
to be delivered even if there are file descriptor ready for I/O.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/