linux-kernel - Re: [PATCH] ASoC: wm_adsp: Fix missing mutex_lock in wm_adsp_write

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]

Date: Thu, 07 Mar 2024 17:43:08 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, alsa-devel@...a-project.org, 
 linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: wm_adsp: Fix missing mutex_lock in
 wm_adsp_write_ctl()

On Thu, 07 Mar 2024 11:02:27 +0000, Richard Fitzgerald wrote:
> wm_adsp_write_ctl() must hold the pwr_lock mutex when calling
> cs_dsp_get_ctl().
> 
> This was previously partially fixed by commit 781118bc2fc1
> ("ASoC: wm_adsp: Fix missing locking in wm_adsp_[read|write]_ctl()")
> but this only put locking around the call to cs_dsp_coeff_write_ctrl(),
> missing the call to cs_dsp_get_ctl().
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: wm_adsp: Fix missing mutex_lock in wm_adsp_write_ctl()
      commit: f193957b0fbbba397c8bddedf158b3bf7e4850fc

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