public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: perf: perf_fuzzer quickly locks up on 4.15-rc7
Date: Tue, 9 Jan 2018 17:14:00 +0100	[thread overview]
Message-ID: <20180109161400.GC2369@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180109151253.GK6176@hirez.programming.kicks-ass.net>

On Tue, Jan 09, 2018 at 04:12:53PM +0100, Peter Zijlstra wrote:

> In any case, I found yet another lockdep splat, trying to figure out wth
> to do about that.

An of course, testing this one yields yet another lockdep splat..
onwards to #3 :/

---
Subject: perf: Fix another perf,trace,cpuhp lock inversion
From: Peter Zijlstra <peterz@infradead.org>
Date: Tue Jan 9 17:07:59 CET 2018

Lockdep complained about:

        perf_trace_init()
#0        mutex_lock(&event_mutex)
          perf_trace_event_init()
            perf_trace_event_reg()
              tp_event->class->reg() := tracepoint_probe_register
#1              mutex_lock(&tracepoints_mutex)
                  trace_point_add_func()
#2                  static_key_enable()



#2	do_cpu_up()
	  perf_event_init_cpu()
#3	    mutex_lock(&pmus_lock)
#4	    mutex_lock(&ctx->mutex)


	perf_ioctl()
#4	  ctx = perf_event_ctx_lock()
	  _perf_iotcl()
	    ftrace_profile_set_filter()
#0	      mutex_lock(&event_mutex)


Fudge it for now by noting that the tracepoint state does not depend
on the event <-> context relation. Ugly though :/

Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
 kernel/events/core.c |   26 ++++++++++++++++++++++++--
 1 file changed, 24 insertions(+), 2 deletions(-)

--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -8525,6 +8525,29 @@ perf_event_set_addr_filter(struct perf_e
 	return ret;
 }
 
+static int
+perf_tracepoint_set_filter(struct perf_event *event, char *filter_str)
+{
+	struct perf_event_context *ctx = event->ctx;
+	int ret;
+
+	/*
+	 * Beware, here be dragons!!
+	 *
+	 * the tracepoint muck will deadlock against ctx->mutex, but the tracepoint
+	 * stuff does not actually need it. So temporarily drop ctx->mutex. As per
+	 * perf_event_ctx_lock() we already have a reference on ctx.
+	 *
+	 * This can result in event getting moved to a different ctx, but that
+	 * does not affect the tracepoint state.
+	 */
+	mutex_unlock(&ctx->mutex);
+	ret = ftrace_profile_set_filter(event, event->attr.config, filter_str);
+	mutex_lock(&ctx->mutex);
+
+	return ret;
+}
+
 static int perf_event_set_filter(struct perf_event *event, void __user *arg)
 {
 	char *filter_str;
@@ -8541,8 +8564,7 @@ static int perf_event_set_filter(struct
 
 	if (IS_ENABLED(CONFIG_EVENT_TRACING) &&
 	    event->attr.type == PERF_TYPE_TRACEPOINT)
-		ret = ftrace_profile_set_filter(event, event->attr.config,
-						filter_str);
+		ret = perf_tracepoint_set_filter(event, filter_str);
 	else if (has_addr_filter(event))
 		ret = perf_event_set_addr_filter(event, filter_str);
 

  parent reply	other threads:[~2018-01-09 16:14 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 16:12 perf: perf_fuzzer quickly locks up on 4.15-rc7 Vince Weaver
2018-01-08 17:30 ` Ingo Molnar
2018-01-08 20:29   ` Vince Weaver
2018-01-09 10:25     ` Peter Zijlstra
2018-01-09 13:26       ` Peter Zijlstra
2018-01-09 13:36         ` Peter Zijlstra
2018-01-09 13:44         ` Vince Weaver
2018-01-09 15:12           ` Peter Zijlstra
2018-01-09 15:24             ` Vince Weaver
2018-01-09 15:33               ` Peter Zijlstra
2018-01-09 15:56                 ` Vince Weaver
2018-01-09 16:05                   ` Peter Zijlstra
2018-01-09 17:07                     ` Josh Poimboeuf
2018-01-11  5:25                       ` Josh Poimboeuf
2018-01-11 19:00                         ` Vince Weaver
2018-01-11 19:21                           ` Josh Poimboeuf
2018-01-11 19:50                             ` Peter Zijlstra
2018-01-11 19:57                               ` Vince Weaver
2018-01-11 20:43                                 ` Vince Weaver
2018-05-01 13:29                             ` perf: fuzzer causes stack going in wrong direction warnings Vince Weaver
2018-05-01 13:58                               ` Josh Poimboeuf
2018-05-01 19:59                                 ` Vince Weaver
2018-05-01 22:04                                   ` Josh Poimboeuf
2018-05-02 20:50                                     ` Josh Poimboeuf
2018-05-04 14:35                                       ` Vince Weaver
2018-05-04 16:25                                         ` Josh Poimboeuf
2018-05-04 17:00                                           ` Vince Weaver
2018-05-05 15:38                                           ` Vince Weaver
2018-05-05 18:29                                             ` Josh Poimboeuf
2018-05-06 23:49                                               ` Josh Poimboeuf
2018-05-10 13:48                                                 ` Peter Zijlstra
2018-05-10 14:27                                                   ` Josh Poimboeuf
2018-05-10 23:16                                                   ` Josh Poimboeuf
2018-01-09 16:16                 ` perf: perf_fuzzer quickly locks up on 4.15-rc7 Ingo Molnar
2018-01-09 16:20                   ` Peter Zijlstra
2018-01-09 17:18                 ` Vince Weaver
2018-01-10 15:28                   ` Vince Weaver
2018-01-09 16:14             ` Peter Zijlstra [this message]
2018-01-09 17:53               ` Steven Rostedt
2018-01-09 18:02                 ` Peter Zijlstra
2018-01-09 18:09                   ` Steven Rostedt
2018-01-09 19:53                     ` Peter Zijlstra
2018-01-11  9:13           ` Peter Zijlstra
2018-01-11 15:26             ` Vince Weaver
2018-01-11 15:38               ` Peter Zijlstra
2018-01-11 16:41                 ` Vince Weaver
2018-01-11 16:58                   ` Vince Weaver
2018-01-11 17:03                     ` Peter Zijlstra
2018-01-11 18:04                       ` Vince Weaver
2018-01-11 18:20                         ` Vince Weaver
2018-01-11 19:01                           ` Peter Zijlstra
2018-01-11 19:11                       ` Peter Zijlstra
2018-01-11 20:15                         ` Vince Weaver
2018-01-11 20:40                           ` Vince Weaver
2018-01-11 20:57                             ` Peter Zijlstra
2018-01-12 19:48                               ` Vince Weaver
2018-01-11 20:42                           ` Peter Zijlstra
2018-01-11 15:29             ` Peter Zijlstra

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=20180109161400.GC2369@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox