linux-kernel - Re: [BUG] 6.16-rc7: lockdep failure with max77620-gpio/max77686-rtc

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

Message-ID: <4f80be02-0bbe-4c10-a3d2-324916ea2ca4@sirena.org.uk>
Date: Thu, 31 Jul 2025 14:18:24 +0100
From: Mark Brown <broonie@...nel.org>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Krzysztof Kozlowski <krzk@...nel.org>,
	Chanwoo Choi <cw00.choi@...sung.com>,
	Alexandre Belloni <alexandre.belloni@...tlin.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Bartosz Golaszewski <brgl@...ev.pl>, linux-gpio@...r.kernel.org,
	linux-rtc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Thierry Reding <treding@...dia.com>
Subject: Re: [BUG] 6.16-rc7: lockdep failure with max77620-gpio/max77686-rtc

On Thu, Jul 31, 2025 at 01:43:14PM +0100, Russell King (Oracle) wrote:
> On Thu, Jul 31, 2025 at 01:31:32PM +0100, Mark Brown wrote:

> > Yes, your analysis is right here - it's not come up before because it's
> > very rare to chain regmap-irq chips.

> Yep, I just changed all the "d" variables in regmap-irq to "ricd"
> (first letter of the each word of the struct name), and lockdep
> confirms that it's the mutex.

> I'm not familiar enough with lockdep to know how to fix this, so what's
> the solution here?

I *think* mutex_lock_nested() is what we're looking for here, with the
depth information from the irq_desc but I'm also not super familiar with
this stuff.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)