linux-kernel - Re: [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: <20120703192652.GH29030@opensource.wolfsonmicro.com>
Date:	Tue, 3 Jul 2012 20:26:52 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Stephen Boyd <sboyd@...eaurora.org>
Cc:	Liam Girdwood <lrg@...com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: Fix recursive mutex lockdep warning

On Mon, Jul 02, 2012 at 07:21:06PM -0700, Stephen Boyd wrote:
> A recursive lockdep warning occurs if you call
> regulator_set_optimum_mode() on a regulator with a supply because
> there is no nesting annotation for the rdev->mutex. To avoid this
> warning, get the supply's load before locking the regulator's
> mutex to avoid grabbing the same class of lock twice.

Applied, thanks.  Though we should probably just remove the optimal mode
stuff on account of the total absence of any users...

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