| 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
| ||
|
Message-ID: <20090205161544.GA24799@redhat.com> Date: Thu, 5 Feb 2009 17:15:44 +0100 From: Oleg Nesterov <oleg@...hat.com> To: Kaz Kylheku <kkylheku@...il.com> Cc: Roland McGrath <roland@...hat.com>, linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Ulrich Drepper <drepper@...hat.com> Subject: Re: main thread pthread_exit/sys_exit bug! On 02/04, Kaz Kylheku wrote: > > On Wed, Feb 4, 2009 at 7:05 PM, Roland McGrath <roland@...hat.com> wrote: > > I haven't seen the clear explanation of what specific actual problems there > > are here. But I'm quite sure this is not the right approach to address them. > > > > Kaz has said things that seemed to imply that the behavior is erratic or > > the semantics are somehow ill-defined when the group leader has died with > > other threads living on. In fact, this case is perfectly well-specified > > and there is no mystery about it. > > I haven't observed anything that could be called erratic. The behavior that > occurs, occurs reliably. Yes we have the bug, and wait_task_stopped() should be fixed. But it is buggy anyway, even if we delay the death of the main thread. But I also think we shouldn't. (and I am sorry, I still can't find the time to redo my old patch, will try to do this asap). Oleg. -- 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/
Powered by blists - more mailing lists