linux-kernel - Re: [PATCH] regulator: Call of_node_put() only once in rzg2l_usb_vbus_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: <172772865592.2147169.15364434698443632490.b4-ty@kernel.org>
Date: Mon, 30 Sep 2024 21:37:35 +0100
From: Mark Brown <broonie@...nel.org>
To: kernel-janitors@...r.kernel.org, Biju Das <biju.das.jz@...renesas.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Markus Elfring <Markus.Elfring@....de>
Cc: LKML <linux-kernel@...r.kernel.org>, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH] regulator: Call of_node_put() only once in
 rzg2l_usb_vbus_regulator_probe()

On Tue, 24 Sep 2024 13:34:45 +0200, Markus Elfring wrote:
> An of_node_put(config.of_node) call was immediately used after a pointer
> check for a devm_regulator_register() call in this function implementation.
> Thus call such a function only once instead directly before the check.
> 
> This issue was transformed by using the Coccinelle software.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: Call of_node_put() only once in rzg2l_usb_vbus_regulator_probe()
      commit: 7368e9f4e25bea507895bf194bd1c72d693840b2

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