From: Peter Zijlstra <peterz@infradead.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
acme@ghostprotocols.net, LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>,
jolsa@redhat.com, vincent.weaver@maine.edu
Subject: Re: perf: recursive locking of ctx->mutex
Date: Fri, 1 May 2015 16:15:57 +0200 [thread overview]
Message-ID: <20150501141557.GC24151@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150501141337.GG5029@twins.programming.kicks-ass.net>
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..
prev parent reply other threads:[~2015-05-01 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 15:12 perf: recursive locking of ctx->mutex Sasha Levin
2015-05-01 14:13 ` Peter Zijlstra
2015-05-01 14:15 ` Peter Zijlstra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150501141557.GC24151@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=davej@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=sasha.levin@oracle.com \
--cc=vincent.weaver@maine.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.