From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [peterz-queue:perf/pmu-unregister] [perf] 24b8359383: WARNING:possible_circular_locking_dependency_detected
Date: Fri, 25 Oct 2024 12:05:12 +0200 [thread overview]
Message-ID: <20241025100512.GJ14555@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <202410251647.21bf487b-lkp@intel.com>
On Fri, Oct 25, 2024 at 04:37:22PM +0800, kernel test robot wrote:
> [ 90.688729][ T589] WARNING: possible circular locking dependency detected
> [ 90.689307][ T589] 6.12.0-rc2-00016-g24b8359383ae #1 Tainted: G T
> [ 90.689852][ T589] ------------------------------------------------------
> [ 90.690348][ T589] trinity-c2/589 is trying to acquire lock:
> [ 90.690768][ T589] ee61f668 (&ctx->mutex){+.+.}-{3:3}, at: perf_event_ctx_lock_nested (kernel/events/core.c:1318)
> [ 90.691425][ T589]
> [ 90.691425][ T589] but task is already holding lock:
> [ 90.691944][ T589] ed2041d4 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff (arch/x86/include/asm/jump_label.h:41 include/linux/jump_label.h:207 include/linux/mmap_lock.h:35 include/linux/mmap_lock.h:123 mm/util.c:586)
> [ 90.692525][ T589]
> [ 90.692525][ T589] which lock already depends on the new lock.
> [ 90.692525][ T589]
> [ 90.693271][ T589]
> [ 90.693271][ T589] the existing dependency chain (in reverse order) is:
> [ 90.693907][ T589]
> [ 90.693907][ T589] -> #1 (&mm->mmap_lock){++++}-{3:3}:
> [ 90.697787][ T589] -> #0 (&ctx->mutex){+.+.}-{3:3}:
> [ 90.707850][ T589] 1 lock held by trinity-c2/589:
> [ 90.708198][ T589] #0: ed2041d4 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff (arch/x86/include/asm/jump_label.h:41 include/linux/jump_label.h:207 include/linux/mmap_lock.h:35 include/linux/mmap_lock.h:123 mm/util.c:586)
> [ 90.708811][ T589]
Damn, I'm an idiot. But also, how did I not manage to trigger this
myself...
Oh well, something to do over the weekend I suppose :/
prev parent reply other threads:[~2024-10-25 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 8:37 [peterz-queue:perf/pmu-unregister] [perf] 24b8359383: WARNING:possible_circular_locking_dependency_detected kernel test robot
2024-10-25 10:05 ` 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=20241025100512.GJ14555@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
/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.