linux-kernel - Re: [peterz-queue:perf/pmu-unregister] [perf] 24b8359383: WARNING:possible_circular_locking_dependency

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20241025100512.GJ14555@noisy.programming.kicks-ass.net>
Date: Fri, 25 Oct 2024 12:05:12 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: kernel test robot <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com, linux-perf-users@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [peterz-queue:perf/pmu-unregister] [perf] 24b8359383:
 WARNING:possible_circular_locking_dependency_detected

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 :/