linux-kernel - Re: [PATCH] ASoC: cs-amp-lib-test: Force test calibration blob entries to be valid

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: <172434346501.724373.2209819895123532015.b4-ty@kernel.org>
Date: Thu, 22 Aug 2024 17:17:45 +0100
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] ASoC: cs-amp-lib-test: Force test calibration blob
 entries to be valid

On Thu, 22 Aug 2024 12:57:25 +0100, Richard Fitzgerald wrote:
> For a normal calibration blob the calTarget values must be non-zero and
> unique, and the calTime values must be non-zero. Don't rely on
> get_random_bytes() to be random enough to guarantee this. Force the
> calTarget and calTime values to be valid while retaining randomness
> in the values.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs-amp-lib-test: Force test calibration blob entries to be valid
      commit: bff980d8d9ca537fd5f3c0e9a99876c1e3713e81

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