linux-kernel - Re: [PATCH] ASoC: codecs: wcd938x: fix codec initialisation race

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: <168814486382.50974.15112012461000088627.b4-ty@kernel.org>
Date:   Fri, 30 Jun 2023 18:07:43 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Johan Hovold <johan+linaro@...nel.org>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        Steev Klimaszewski <steev@...i.org>
Subject: Re: [PATCH] ASoC: codecs: wcd938x: fix codec initialisation race

On Fri, 30 Jun 2023 14:03:18 +0200, Johan Hovold wrote:
> Make sure to resume the codec and soundwire device before trying to read
> the codec variant and configure the device during component probe.
> 
> This specifically avoids interpreting (a masked and shifted) -EBUSY
> errno as the variant:
> 
> 	wcd938x_codec audio-codec: ASoC: error at soc_component_read_no_lock on audio-codec for register: [0x000034b0] -16
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: codecs: wcd938x: fix codec initialisation race
      commit: 85a61b1ce461a3f62f1019e5e6423c393c542bff

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