linux-kernel - Re: [PATCH] regulator: core: Fix deadlock in create

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <174127743310.139067.18421528658328591081.b4-ty@kernel.org>
Date: Thu, 06 Mar 2025 16:10:33 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Douglas Anderson <dianders@...omium.org>, 
 David Collins <quic_collinsd@...cinc.com>, 
 Ludvig Pärsson <ludvig.parsson@...s.com>
Cc: linux-kernel@...r.kernel.org, kernel@...s.com
Subject: Re: [PATCH] regulator: core: Fix deadlock in create_regulator()

On Wed, 05 Mar 2025 17:05:04 +0100, Ludvig Pärsson wrote:
> Currently, we are unnecessarily holding a regulator_ww_class_mutex lock
> when creating debugfs entries for a newly created regulator. This was
> brought up as a concern in the discussion in commit cba6cfdc7c3f
> ("regulator: core: Avoid lockdep reports when resolving supplies").
> 
> This causes the following lockdep splat after executing
> `ls /sys/kernel/debug` on my platform:
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: core: Fix deadlock in create_regulator()
      commit: 1c81a8c78ae653f3a21cde0f37a91f1b22b7d2fb

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