linux-kernel - Re: [PATCH 09/11] job control: reorganize wait_task

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110512160253.GK1030@htj.dyndns.org>
Date:	Thu, 12 May 2011 18:02:53 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	jan.kratochvil@...hat.com, vda.linux@...glemail.com,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, indan@....nu
Subject: Re: [PATCH 09/11] job control: reorganize wait_task_stopped()

Hello,

On Thu, May 12, 2011 at 05:42:47PM +0200, Oleg Nesterov wrote:
> On 05/11, Tejun Heo wrote:
> >
> > > Can't we push this patch ahead of these changes? I can merge it into
> > > ptrace branch.
> >
> > It doesn't really fix the problem tho.  The whole thing is full of
> > holes
> 
> Hmm. Could you explain?  (unless you mean ptrace holes)

I meant other cases, RUNNING -> STOPPED and EXIT_* transitions.
Sleeping wait(2) is reliable without grabbing siglock thanks to
setting TASK_INTERRUPTIBLE on start and events waking up the waiter
after updating the state, so wait(2) is guaranteed to check the states
at least once after change actually has happened.

WNOHANG disables that mechanism.  We probably can add another set of
memory barrier hackery to fix that, but that's gonna be ugly.

Thanks.

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