linux-kernel - Re: [PATCH] firmware: cs_dsp: rate-limit log messages in KUnit builds

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: <177012031931.85387.7521440900629176229.b4-ty@kernel.org>
Date: Tue, 03 Feb 2026 12:05:19 +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: rate-limit log messages in KUnit
 builds

On Fri, 30 Jan 2026 17:12:56 +0000, Richard Fitzgerald wrote:
> Use the dev_*_ratelimit() macros if the cs_dsp KUnit tests are enabled
> in the build, and allow the KUnit tests to disable message output.
> 
> Some of the KUnit tests cause a very large number of log messages from
> cs_dsp, because the tests perform many different test cases. This could
> cause some lines to be dropped from the kernel log. Dropped lines can
> prevent the KUnit wrappers from parsing the ktap output in the dmesg log.
> 
> [...]

Applied to

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

Thanks!

[1/1] firmware: cs_dsp: rate-limit log messages in KUnit builds
      commit: 10db9f6899dd3a2dfd26efd40afd308891dc44a8

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