linux-kernel - Re: [PATCH] firmware: cs_dsp: Use kvzalloc() to allocate control caches

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: <176426137528.95122.10728874044259284349.b4-ty@kernel.org>
Date: Thu, 27 Nov 2025 16:36:15 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH] firmware: cs_dsp: Use kvzalloc() to allocate control
 caches

On Thu, 27 Nov 2025 10:39:47 +0000, Richard Fitzgerald wrote:
> Use kvzalloc() instead of kzalloc() to allocate memory to cache the
> content of a firmware control.
> 
> Most firmware controls are only small, typically a few bytes. But on
> some firmware there can be much larger controls for coefficient or
> model data.
> 
> [...]

Applied to

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

Thanks!

[1/1] firmware: cs_dsp: Use kvzalloc() to allocate control caches
      commit: c45d5d9803a4fb7d3e7f590094b7a2abcfe74ef6

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