linux-kernel - Re: perf: recursive locking of ctx->mutex

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] [day] [month] [year] [list]

Message-ID: <20150501141557.GC24151@twins.programming.kicks-ass.net>
Date:	Fri, 1 May 2015 16:15:57 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Sasha Levin <sasha.levin@...cle.com>
Cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...nel.org>,
	Steven Rostedt <rostedt@...dmis.org>, acme@...stprotocols.net,
	LKML <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>, jolsa@...hat.com,
	vincent.weaver@...ne.edu
Subject: Re: perf: recursive locking of ctx->mutex

On Fri, May 01, 2015 at 04:13:37PM +0200, Peter Zijlstra wrote:
> 
> A little something like so should cure that me thinks.
> 
> I would much appreciate other people reviewing this with care though; my
> snot addled brain isn't too bright.
> 
> 
> @@ -8728,7 +8753,7 @@ static int perf_event_init_context(struc
>  	 * Lock the parent list. No need to lock the child - not PID
>  	 * hashed yet and not running, so nobody can access it.
>  	 */
> -	mutex_lock(&parent_ctx->mutex);
> +	mutex_lock_nested(&parent_ctx->mutex);
>  
>  	/*
>  	 * We dont have to disable NMIs - we are only looking at

It will help with building to not apply this last hunk..
--
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/