linux-kernel - Re: [PATCH][RFC] Always unlock 'tasklist_lock' in kernel/exit.c::do

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: <20101220215432.af5798d5.akpm@linux-foundation.org>
Date:	Mon, 20 Dec 2010 21:54:32 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jesper Juhl <jj@...osbits.net>
Cc:	linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...hat.com>,
	Roland McGrath <roland@...hat.com>,
	Ingo Molnar <mingo@...e.hu>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: [PATCH][RFC] Always unlock 'tasklist_lock' in
 kernel/exit.c::do_wait()

On Mon, 20 Dec 2010 23:30:38 +0100 (CET) Jesper Juhl <jj@...osbits.net> wrote:

> The Coverity checker spotted this. I think it has a point, but I'm not 
> intimate with this code so there could be somethingI'm missing.
> 
> It seems that kernel/exit.c::do_wait() does not always release 
> 'tasklist_lock'.

do_wait_thread() and ptrace_do_wait() will have released tasklist_lock
if they returned non-zero.

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