linux-kernel - Re: [PATCH] regulator: core: use kfree_const() to free space conditionally

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]

Message-Id: <166921373057.240778.13837593639387001474.b4-ty@kernel.org>
Date:   Wed, 23 Nov 2022 14:28:50 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Wang ShaoBo <bobo.shaobowang@...wei.com>
Cc:     lgirdwood@...il.com, liwei391@...wei.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: core: use kfree_const() to free space conditionally

On Wed, 23 Nov 2022 11:46:16 +0800, Wang ShaoBo wrote:
> Use kfree_const() to free supply_name conditionally in create_regulator()
> as supply_name may be allocated from kmalloc() or directly from .rodata
> section.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: core: use kfree_const() to free space conditionally
      commit: dc8d006d15b623c1d80b90b45d6dcb6e890dad09

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