Weird signal handling bug 221635

[Matt Zimmerman]

On Wed, Apr 30, 2008 at 11:15:23AM +0100, Colin Watson wrote:
> While I've weakened the assertion upstream for other reasons (i.e. the
> assert function isn't async-signal-safe, though that wouldn't cause this
> bug), and may well propose this for 8.04.1, it worries me that a signal
> handler is being called with a signal number that wasn't requested by
> sigaction; the consequences might be more serious elsewhere. Can anyone
> see anything wrong with my code, or think of a kernel bug that might
> cause this?

My only guess would be some sloppy handling of a struct sigaction somewhere
which led to it being re-used with old data.  I noticed the code saves and
restores the SIGCHLD action a few times...

-- 
 - mdz