linux-kernel - Re: [PATCH] firmware: cs_dsp: Take pwr_lock around reading controls debugfs

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: <176426137654.95122.11964232571173821588.b4-ty@kernel.org>
Date: Thu, 27 Nov 2025 16:36:16 +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: Take pwr_lock around reading
 controls debugfs

On Thu, 27 Nov 2025 11:32:38 +0000, Richard Fitzgerald wrote:
> In cs_dsp_debugfs_read_controls_show() take the pwr_lock mutex
> around the list walk. This protects against debugfs returning
> a partial set of new controls if those controls are being added
> to the list while it is being walked.
> 
> Controls are never deleted from this list, and are only added to
> the end of the list. So there was never a danger of following a
> stale pointer to garbage.
> 
> [...]

Applied to

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

Thanks!

[1/1] firmware: cs_dsp: Take pwr_lock around reading controls debugfs
      commit: ed6e90cb9fe53aba4750be50c1a355d676b7d69c

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