ASoC: cs-amp-lib-test: Force test calibration blob entries to be valid
Subsystems (3)
Richard Fitzgerald
maintainerPATCH 1/1 ASoC: cs-amp-lib-test: Force test calibration blob entries to be valid
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.
--- sound/soc/codecs/cs-amp-lib-test.c | 9 +++++++++ 1 file changed, 9 insertions(+)
sound/soc/codecs/cs-amp-lib-test.c +9 -0
@@ -38,6 +38,7 @@ static void cs_amp_lib_test_init_dummy_cal_blob(struct kunit *test, int num_amps {struct cs_amp_lib_test_priv *priv = test->priv;unsigned int blob_size; +int i; blob_size = offsetof(struct cirrus_amp_efi_data , data) +sizeof (struct cirrus_amp_cal_data ) * num_amps;
@@ -49,6 +50,14 @@ static void cs_amp_lib_test_init_dummy_cal_blob(struct kunit *test, int num_amps priv->cal_blob->count = num_amps;get_random_bytes (priv->cal_blob->data,sizeof (struct cirrus_amp_cal_data ) * num_amps); + +/* Ensure all timestamps are non-zero to mark the entry valid. */ +for (i =0 ; i < num_amps; i++) + priv->cal_blob->data[i].calTime[0 ] |=1 ; + +/* Ensure that all UIDs are non-zero and unique. */ +for (i =0 ; i < num_amps; i++) + *(u8 *)&priv->cal_blob->data[i].calTarget[0 ] = i +1 ; }static u64 cs_amp_lib_test_get_target_uid (struct kunit *test)
Signature · 1 line
2.39.2
Mark Brown
maintainerQuoted 8 lines · Richard Fitzgerald
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