linux-kernel - Re: [PATCH] ASoC: rt5645: Fix deadlock in rt5645_jack_detect

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: <170769945366.2475236.12473268972923112116.b4-ty@kernel.org>
Date: Mon, 12 Feb 2024 00:57:33 +0000
From: Mark Brown <broonie@...nel.org>
To: Oder Chiou <oder_chiou@...ltek.com>, 
 Alexey Khoroshilov <khoroshilov@...ras.ru>
Cc: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Shuming Fan <shumingf@...ltek.com>, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 lvc-project@...uxtesting.org
Subject: Re: [PATCH] ASoC: rt5645: Fix deadlock in
 rt5645_jack_detect_work()

On Sun, 11 Feb 2024 12:58:34 +0300, Alexey Khoroshilov wrote:
> There is a path in rt5645_jack_detect_work(), where rt5645->jd_mutex
> is left locked forever. That may lead to deadlock
> when rt5645_jack_detect_work() is called for the second time.
> 
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: rt5645: Fix deadlock in rt5645_jack_detect_work()
      commit: 6ef5d5b92f7117b324efaac72b3db27ae8bb3082

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