linux-kernel - Re: [PATCH] ASoC: soc-pcm.c: Clear DAIs parameters after stream

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:   Wed, 07 Dec 2022 21:04:59 +0000
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        Chancel Liu <chancel.liu@....com>
Subject: Re: [PATCH] ASoC: soc-pcm.c: Clear DAIs parameters after
 stream_active is updated

On Mon, 28 Nov 2022 14:09:50 +0800, Chancel Liu wrote:
> DAIs parameters should be cleared if there's no active stream. Before,
> we implemented it in soc_pcm_hw_free() by detecting stream_active. If
> the running stream is the last active stream, we're going to clear
> parameters.
> 
> However it will cause DAIs parameters never be cleared if there're
> more than one stream. For example, we have stream1 and stream2 about
> to stop. stream2 executes soc_pcm_hw_free() before stream1 executes
> soc_pcm_close(). At the moment, stream2 should clear DAIs parameters.
> Since stream_active is not yet updated by stream1 in soc_pcm_close(),
> stream2 will not clear DAIs parameters. In result both stream1 and
> stream2 don't clear the parameters.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: soc-pcm.c: Clear DAIs parameters after stream_active is updated
      commit: 1da681e52853f0abfbfff8c69833d31e538ff9c0

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