linux-kernel - Re: [PATCH 0/5] kill the racy EXIT_ZOMBIE->EXIT_DEAD->EXIT

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: <20140224155121.GA10545@redhat.com>
Date:	Mon, 24 Feb 2014 16:51:21 +0100
From:	Oleg Nesterov <oleg@...hat.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Al Viro <viro@...IV.linux.org.uk>,
	Jan Kratochvil <jan.kratochvil@...hat.com>,
	Lennart Poettering <lpoetter@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Michal Schmidt <mschmidt@...hat.com>,
	Roland McGrath <roland@...k.frob.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] kill the racy EXIT_ZOMBIE->EXIT_DEAD->EXIT_ZOMBIE
	transition

On 02/20, Tejun Heo wrote:
>
> On Thu, Feb 20, 2014 at 06:38:38PM +0100, Oleg Nesterov wrote:
> > Tejun, unless I missed something WSTOPPED logic is broken if a process
> > has a zombie/ptraced leader, "A zombie ptracee is only visible to its
> > ptracer" is wrong in this case. Plus perhaps some cleanups make sense.
>
> Heh, I already forgot most details about ptrace. :)

This is mostly about do_wait(), although yes, !ptrace case looks fine.
And it turns out, I forgot these details too.

> Is it something
> urgent?

No, please forget. But it seems that wait_consider_task(zombie_leader)
is very wrong wrt zombie leaders. WSTOPPED is simple, but I am still
trying to find a simple fix for other problems. And the main problem,
of course, is that this API is broken and we can't fix it.

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/