On Thu, 15 Dec 2022 11:46:46 +0100, Johan Hovold wrote:
> When updating the operating mode as part of regulator enable, the caller
> has already locked the regulator tree and drms_uA_update() must not try
> to do the same in order not to trigger a deadlock.
>
> The lock inversion is reported by lockdep as:
>
> ======================================================
> WARNING: possible circular locking dependency detected
> 6.1.0-next-20221215 #142 Not tainted
> ------------------------------------------------------
> udevd/154 is trying to acquire lock:
> ffffc11f123d7e50 (regulator_list_mutex){+.+.}-{3:3}, at: regulator_lock_dependent+0x54/0x280
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: core: fix deadlock on regulator enable
commit: cb3543cff90a4448ed560ac86c98033ad5fecda9
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
