linux-kernel - Re: [PATCH] regulator: core: Fix enable_count imbalance with EXCLUSIVE

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]

Date:   Thu, 05 May 2022 16:12:23 +0100
From:   Mark Brown <broonie@...nel.org>
To:     zev@...ilderbeest.net, lgirdwood@...il.com
Cc:     linux-kernel@...r.kernel.org, dianders@...omium.org
Subject: Re: [PATCH] regulator: core: Fix enable_count imbalance with EXCLUSIVE_GET

On Wed, 4 May 2022 21:31:52 -0700, Zev Weiss wrote:
> Since the introduction of regulator->enable_count, a driver that did
> an exclusive get on an already-enabled regulator would end up with
> enable_count initialized to 0 but rdev->use_count initialized to 1.
> With that starting point the regulator is effectively stuck enabled,
> because if the driver attempted to disable it it would fail the
> enable_count underflow check in _regulator_handle_consumer_disable().
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: core: Fix enable_count imbalance with EXCLUSIVE_GET
      commit: c3e3ca05dae37f8f74bb80358efd540911cbc2c8

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