linux-kernel - [PATCH 0/2] regmap: Fix lockdep warnings for nested regmap-irqs

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-next>] [day] [month] [year] [list]

Message-Id: <20250731-regmap-irq-nesting-v1-0-98b4d1bf20f0@kernel.org>
Date: Thu, 31 Jul 2025 21:38:17 +0100
From: Mark Brown <broonie@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
 "Rafael J. Wysocki" <rafael@...nel.org>, Danilo Krummrich <dakr@...nel.org>
Cc: "Russell King (Oracle)" <linux@...linux.org.uk>, 
 linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: [PATCH 0/2] regmap: Fix lockdep warnings for nested regmap-irqs

Russell King reported that lockdep warns when it sees nested regmap-irq
interrupt controllers since it defaults to using a single lock class for
all mutexes allocated from a single place in the code.  We end up with
both the parent and child regmap-irq locked simultaneously.  The second
patch here uses an explicit lockdep key to disambiguate things for
regmap, the first adds missing mutex cleanup which I noticed while
writing that patch.

I don't have an affected system so this is written blind, I should
really write some KUnit tests for regmap-irq but didn't yet.

Signed-off-by: Mark Brown <broonie@...nel.org>
---
Mark Brown (2):
      regmap: irq: Free the regmap-irq mutex
      regmap: irq: Avoid lockdep warnings with nested regmap-irq chips

 drivers/base/regmap/regmap-irq.c | 30 +++++++++++++++++++++---------
 1 file changed, 21 insertions(+), 9 deletions(-)
---
base-commit: 038d61fd642278bab63ee8ef722c50d10ab01e8f
change-id: 20250731-regmap-irq-nesting-40970c711fd2

Best regards,
--  
Mark Brown <broonie@...nel.org>