linux-kernel - Re: [PATCH] ASoC: mediatek: mt6359: Fix unexpected error in bind/unbind flow

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: <163171901944.9674.15745923942801327979.b4-ty@kernel.org>
Date:   Wed, 15 Sep 2021 16:21:50 +0100
From:   Mark Brown <broonie@...nel.org>
To:     tiwai@...e.com, Trevor Wu <trevor.wu@...iatek.com>,
        matthias.bgg@...il.com
Cc:     Mark Brown <broonie@...nel.org>, tzungbi@...gle.com,
        alsa-devel@...a-project.org, chipeng.chang@...iatek.com,
        linux-mediatek@...ts.infradead.org, shane.chien@...iatek.com,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        jiaxin.yu@...iatek.com
Subject: Re: [PATCH] ASoC: mediatek: mt6359: Fix unexpected error in bind/unbind flow

On Wed, 15 Sep 2021 11:46:59 +0800, Trevor Wu wrote:
> mt6359-sound is a MFD driver. Because its regmap is retrieved from its
> parent, it shouldn't be freed in mt6359-sound driver.
> 
> snd_soc_component_exit_regmap() will do regmap_exit(), this results in
> unexpected results if sound card unregister flow is invoked when users
> try to bind/unbind audio codec.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: mediatek: mt6359: Fix unexpected error in bind/unbind flow
      commit: 6d66c5ccf5cb8af866fe2bb014098a3dd7bfa3cc

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