linux-kernel - Re: [PATCH] ASoC: codecs: wcd937x: Fix error handling in wcd937x codec driver

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: <176363161218.559933.9857333808970075663.b4-ty@kernel.org>
Date: Thu, 20 Nov 2025 09:40:12 +0000
From: Mark Brown <broonie@...nel.org>
To: srini@...nel.org, lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 dmitry.baryshkov@....qualcomm.com, Ma Ke <make24@...as.ac.cn>
Cc: linux-sound@...r.kernel.org, linux-arm-msm@...r.kernel.org, 
 linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, 
 stable@...r.kernel.org
Subject: Re: [PATCH] ASoC: codecs: wcd937x: Fix error handling in wcd937x
 codec driver

On Sun, 16 Nov 2025 14:16:23 +0800, Ma Ke wrote:
> In wcd937x_bind(), the driver calls of_sdw_find_device_by_node() to
> obtain references to RX and TX SoundWire devices, which increment the
> device reference counts. However, the corresponding put_device() are
> missing in both the error paths and the normal unbind path in
> wcd937x_unbind().
> 
> Add proper error handling with put_device() calls in all error paths
> of wcd937x_bind() and ensure devices are released in wcd937x_unbind().
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: codecs: wcd937x: Fix error handling in wcd937x codec driver
      commit: 578ccfe344c5f421c2c6343b872995b397ffd3ff

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