linux-kernel - Re: [RESEND][RFC PATCH v2] waitfd

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]

Message-ID: <alpine.DEB.1.10.0901101511590.22208@alien.or.mcafeemobile.com>
Date:	Sat, 10 Jan 2009 15:14:01 -0800 (PST)
From:	Davide Libenzi <davidel@...ilserver.org>
To:	Oleg Nesterov <oleg@...hat.com>
cc:	Scott James Remnant <scott@...onical.com>,
	Roland McGrath <roland@...hat.com>,
	Ingo Molnar <mingo@...e.hu>, Casey Dahlin <cdahlin@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [RESEND][RFC PATCH v2] waitfd

On Sat, 10 Jan 2009, Oleg Nesterov wrote:

> > Thus:
> >
> >  - child process #1 dies
> >  - main loop woken up by SIGCHLD
> >  - pending status of signal cleared
> >  - enter wait loop
> >  - child process #2 dies
> >  - SIGCHLD pending again
> >  - waitpid() called first time, child process #1 reaped
> >  - waitpid() called second time, child process #2 reaped
> >    (SIGCHLD still pending)
> >  - waitpid() called third time, no child processes remain
> >  - exit wait loop
> >  - back to top of main loop, immediately woken up by pending SIGCHLD
> >  - pending status of signal cleared
> >  - enter wait loop
> >  - waitpid() called first time, but no child processes remain
> >    (we reaped it last time round)
> >  - exit wait loop
> >  - back to top of main loop, sleep
> 
> Scott, I don't really understand why are you trying to explain this
> all to me. I do understand this. At least I hope ;)

Indeed :)
Scott, you're teaching Linux signals to the guy that is likely the 
de-facto mantainer of the subsystem. See the irony?



- Davide


--
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/