public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: syzbot 
	<bot+f67ad450a4bd1e42a7bd09f592904b15be39db7a@syzkaller.appspotmail.com>
Cc: acme@kernel.org, alexander.shishkin@linux.intel.com,
	linux-kernel@vger.kernel.org, mingo@redhat.com,
	syzkaller-bugs@googlegroups.com,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: possible deadlock in perf_event_ctx_lock_nested
Date: Fri, 27 Oct 2017 17:11:37 +0200	[thread overview]
Message-ID: <20171027151137.GC3165@worktop.lehotels.local> (raw)
In-Reply-To: <001a11448f6c0346ec055c831a71@google.com>

On Fri, Oct 27, 2017 at 01:30:30AM -0700, syzbot wrote:

> ======================================================
> WARNING: possible circular locking dependency detected
> 4.13.0-next-20170911+ #19 Not tainted
> ------------------------------------------------------
> syz-executor2/12380 is trying to acquire lock:
>  (&ctx->mutex){+.+.}, at: [<ffffffff8180923c>]
> perf_event_ctx_lock_nested+0x1dc/0x3c0 kernel/events/core.c:1210
> 
> but task is already holding lock:
>  (&pipe->mutex/1){+.+.}, at: [<ffffffff81ac0fa6>] pipe_lock_nested
> fs/pipe.c:66 [inline]
>  (&pipe->mutex/1){+.+.}, at: [<ffffffff81ac0fa6>] pipe_lock+0x56/0x70
> fs/pipe.c:74
> 
> which lock already depends on the new lock.


ARRGH!!

that translates like the below, which is an absolute maze and requires
at least 5 concurrent callstacks, possibly more.

We already had a lot of fun with hotplug-perf-ftrace, but the below
contains more. Let me try and page that previous crap back.



	perf_ioctl()
#0	  perf_event_ctx_lock()		[ctx->mutex]
	  perf_event_set_filter  
#1	    ftrace_profile_set_filter   [event_mutex]
		



	sys_perf_event_open
	  ...
	  perf_trace_init
#1	    mutex_lock [event_mutex]
	    trace_event_reg
	      tracepoint_probe_register
#2		mutex_lock() [tracepoints_mutex]
		tracepoint_add_func()
#3		  static_key_slow_inc()	[cpuhotplug_lock]
	




	cpuhp_setup_state_nocalls
#3	  cpus_read_lock	[cpuhotplug_lock]
	    __cpuhp_setup_state_cpuslocked
#4	      mutex_lock	[cpuhp_state_mutex]
	      cpuhp_issue_call
#5		cpuhp_invoke_ap_callback()	[cpuhp_state]


#5	cpuhp_invoke_callback [cpuhp_state]
	  ...
	    devtmpfs_create_node
#6	      wait_for_completion()	[&req.done]

						devtmpfsd
						  handle_create
#7						    filename_create [sb_writers]
#6						  complete [&req.done]
							





	do_splice
#7	  file_start_write() [sb_writers]
	  do_splice_from
	    iter_file_splice_write
#8	      pipe_lock [pipe->mutex]





	do_splice
#8	  pipe_lock	[pipe->mutex]
	  do_splice_to
	    ...
#0	      perf_read() [ctx->mutex]
		

  parent reply	other threads:[~2017-10-27 15:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001a11448f6c0346ec055c831a71@google.com>
2017-10-27  8:31 ` possible deadlock in perf_event_ctx_lock_nested Dmitry Vyukov
2017-10-27 15:11 ` Peter Zijlstra [this message]
2017-10-27 15:33   ` Peter Zijlstra
2018-02-12 15:04     ` Dmitry Vyukov
2018-02-14 14:00       ` Dmitry Vyukov

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=20171027151137.GC3165@worktop.lehotels.local \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bot+f67ad450a4bd1e42a7bd09f592904b15be39db7a@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    /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