linux-kernel - Re: [PATCH] firmware: cs_dsp: Add some sanity-checking to test harness

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: <174483464915.868862.8222881008352182759.b4-ty@kernel.org>
Date: Wed, 16 Apr 2025 21:17:29 +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] firmware: cs_dsp: Add some sanity-checking to test
 harness

On Wed, 16 Apr 2025 13:24:22 +0100, Richard Fitzgerald wrote:
> Add sanity checking to some test harness functions to help catch bugs
> in the test code. This consists of checking the range of some arguments
> and checking that reads from the dummy regmap succeed.
> 
> Most of the harness code already had sanity-checking but there were a
> few places where it was missing or was assumed that the test could be
> trusted to pass valid values.
> 
> [...]

Applied to

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

Thanks!

[1/1] firmware: cs_dsp: Add some sanity-checking to test harness
      commit: 4308487b29f98785ef50dd82fdfca382134b33e7

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