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

Message-ID: <55C349C2.1020009@linaro.org>
Date:	Thu, 06 Aug 2015 12:49:22 +0100
From:	Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:	Mark Brown <broonie@...nel.org>
CC:	Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] regulator: Fix recursive mutex lockdep warning



On 06/08/15 12:40, Mark Brown wrote:
> On Thu, Aug 06, 2015 at 12:01:29PM +0100, Srinivas Kandagatla wrote:
>> On 06/08/15 10:43, Mark Brown wrote:
>
>>> like what we have for regmaps with a class per regulator or something
>
>> 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!"



>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/