linux-kernel - Re: [RFC PATCH] regulator: Fix recursive mutex lockdep warning

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: <20150807141258.GH10301@sirena.org.uk>
Date:	Fri, 7 Aug 2015 15:12:58 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:	Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] regulator: Fix recursive mutex lockdep warning

On Thu, Aug 06, 2015 at 12:49:22PM +0100, Srinivas Kandagatla wrote:
> On 06/08/15 12:40, Mark Brown wrote:

> >>lock_class per regulator makes more sense, I will try to cookup an RFC
> >>patch.

> >There's an issue there with all lock classes needing to be statically
> >allocated which makes things a bit tricky.

> Yes, just realized it with "BUG: key edadc07c not in .data!"

Yeah, it's a bit nasty.  We went round this a bit with regmap and
unfortunately didn't manage to come up with any great ideas.  The regmap
workaround just landed in my tree, I'm not sure it's really great for
regulator though.

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