linux-kernel - Re: [PATCH] regulator: bd718x7: Use kcalloc() instead of kzalloc()

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: <175561865630.183354.7456857095894517337.b4-ty@kernel.org>
Date: Tue, 19 Aug 2025 16:50:56 +0100
From: Mark Brown <broonie@...nel.org>
To: Matti Vaittinen <mazziesaccount@...il.com>, 
 Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org, 
 Qianfeng Rong <rongqianfeng@...o.com>
Subject: Re: [PATCH] regulator: bd718x7: Use kcalloc() instead of kzalloc()

On Sun, 17 Aug 2025 22:23:27 +0800, Qianfeng Rong wrote:
> Replace calls of 'devm_kzalloc(dev, count * sizeof([type]), flags)'
> with 'devm_kcalloc(dev, count, sizeof([type]), flags)' in
> setup_feedback_loop() for safer memory allocation with built-in
> overflow protection.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: bd718x7: Use kcalloc() instead of kzalloc()
      commit: 550bc517e59347b3b1af7d290eac4fb1411a3d4e

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