linux-kernel - Re: [PATCH] regulator: of: Implement the unwind path of of_regulator

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] [day] [month] [year] [list]

Message-Id: <173625182449.29779.14024500020318513328.b4-ty@kernel.org>
Date: Tue, 07 Jan 2025 12:10:24 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, Joe Hattori <joe@...is.s.u-tokyo.ac.jp>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: of: Implement the unwind path of
 of_regulator_match()

On Sat, 04 Jan 2025 17:04:53 +0900, Joe Hattori wrote:
> of_regulator_match() does not release the OF node reference in the error
> path, resulting in an OF node leak. Therefore, call of_node_put() on the
> obtained nodes before returning the EINVAL error.
> 
> Since it is possible that some drivers call this function and do not
> exit on failure, such as s2mps11_pmic_driver, clear the init_data and
> of_node in the error path.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: of: Implement the unwind path of of_regulator_match()
      commit: dddca3b2fc676113c58b04aaefe84bfb958ac83e

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