linux-kernel - Re: [PATCH] ASoC: qdsp6: q6asm-dai: fix q6asm_dai_compr_set

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: <174310990724.446560.8160330650752927571.b4-ty@kernel.org>
Date: Thu, 27 Mar 2025 21:11:47 +0000
From: Mark Brown <broonie@...nel.org>
To: srinivas.kandagatla@...aro.org, linux-sound@...r.kernel.org, 
 Alexey Klimov <alexey.klimov@...aro.org>
Cc: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 krzysztof.kozlowski@...aro.org, pierre-louis.bossart@...ux.dev, 
 vkoul@...nel.org, linux-arm-msm@...r.kernel.org, 
 linux-kernel@...r.kernel.org, stable@...r.kernel.org, 
 dmitry.baryshkov@....qualcomm.com
Subject: Re: [PATCH] ASoC: qdsp6: q6asm-dai: fix q6asm_dai_compr_set_params
 error path

On Thu, 27 Mar 2025 15:46:50 +0000, Alexey Klimov wrote:
> In case of attempts to compress playback something, for instance,
> when audio routing is not set up correctly, the audio DSP is left in
> inconsistent state because we are not doing the correct things in
> the error path of q6asm_dai_compr_set_params().
> 
> So, when routing is not set up and compress playback is attempted
> the following errors are present (simplified log):
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: qdsp6: q6asm-dai: fix q6asm_dai_compr_set_params error path
      commit: 7eccc86e90f04a0d758d16c08627a620ac59604d

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