Re: [PATCH v1] regulator: core: Fix slab-out-of-bounds in regulator_unlock_recursive()

[Mark Brown]

On Mon, 31 Aug 2020 23:43:35 +0300, Dmitry Osipenko wrote:
> The recent commit 7d8196641ee1 ("regulator: Remove pointer table
> overallocation") changed the size of coupled_rdevs and now KASAN is able
> to detect slab-out-of-bounds problem in regulator_unlock_recursive(),
> which is a legit problem caused by a typo in the code. The recursive
> unlock function uses n_coupled value of a parent regulator for unlocking
> supply regulator, while supply's n_coupled should be used. In practice
> problem may only affect platforms that use coupled regulators.

Applied to

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

Thanks!

[1/1] regulator: core: Fix slab-out-of-bounds in regulator_unlock_recursive()
      commit: 0a7416f94707c60b9f66b01c0a505b7e41375f3a

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