Re: Fix signalfd interaction with thread-private signals

Davide Libenzi
2007-06-19T23:16:44Z

On Wed, 20 Jun 2007, Oleg Nesterov wrote:

> Well, I think the kernel doesn't make any assumptions on that. It can't
> guarantee the signal will be actually dequeued, to begin with.
>
> (That said, I probably missed something, in that case I'd like to be
> educated. This is the real reason why I am making the noise :)

What happens if a task gets a page fault that results in a SIGSEGV, and
another task steals the SIGSEGV using a signalfd, before the faulted task
has the chance to get into do_notify_resume() and notice it? ;)

- Davide