public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: hpa@zytor.com, mingo@kernel.org, tglx@linutronix.de,
	linux-kernel@vger.kernel.org, rostedt@goodmis.org,
	torvalds@linux-foundation.org
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/urgent] perf/core: Fix lock inversion between perf,trace,cpuhp
Date: Wed, 24 Jan 2018 12:36:29 +0100	[thread overview]
Message-ID: <20180124113629.GS2228@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <tip-25695067c32e34047b5490436a90af507fda1c2e@git.kernel.org>

On Wed, Jan 24, 2018 at 02:39:16AM -0800, tip-bot for Peter Zijlstra wrote:
> Commit-ID:  25695067c32e34047b5490436a90af507fda1c2e
> Gitweb:     https://git.kernel.org/tip/25695067c32e34047b5490436a90af507fda1c2e
> Author:     Peter Zijlstra <peterz@infradead.org>
> AuthorDate: Tue, 9 Jan 2018 13:10:30 +0100
> Committer:  Ingo Molnar <mingo@kernel.org>
> CommitDate: Wed, 24 Jan 2018 10:07:23 +0100
> 
> perf/core: Fix lock inversion between perf,trace,cpuhp
> 
> Lockdep gifted us with noticing the following race:
> 
>         perf_trace_init()
>           perf_trace_event_init()
>             perf_trace_event_reg()
>               tp_event->class->reg() := tracepoint_probe_register
>                   trace_point_add_func()
> 
>           perf_event_init_cpu()
> 
>         perf_event_task_disable()
>           mutex_lock(&current->perf_event_mutex)
> 
>         do_exit()
>           task_work_run()
>             __fput()
>               perf_release()
>                 perf_event_release_kernel()
>                   free_event()
>                     _free_event()
>                       event->destroy() := perf_trace_destroy
> 

You seem to have lost part of the Changelog, mine looks like:

        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_event_task_disable()
          mutex_lock(&current->perf_event_mutex)
#4        ctx = perf_event_ctx_lock()
#5        perf_event_for_each_child()


        do_exit()
          task_work_run()
            __fput()
              perf_release()
                perf_event_release_kernel()
#4                mutex_lock(&ctx->mutex)
#5                mutex_lock(&event->child_mutex)
                  free_event()
                    _free_event()
                      event->destroy() := perf_trace_destroy
#0                      mutex_lock(&event_mutex);



Which shows an actual deadlock.

       reply	other threads:[~2018-01-24 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tip-25695067c32e34047b5490436a90af507fda1c2e@git.kernel.org>
2018-01-24 11:36 ` Peter Zijlstra [this message]
2018-01-24 15:32   ` [tip:perf/urgent] perf/core: Fix lock inversion between perf,trace,cpuhp Ingo Molnar
2018-01-24 16:57     ` Linus Torvalds
2018-01-24 17:42       ` Steven Rostedt

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=20180124113629.GS2228@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /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