linux-kernel - Re: [PATCH] staging: sound: Adjust mutex unlock order

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: <aIi2mfHOksrr5RNB@duo.ucw.cz>
Date: Tue, 29 Jul 2025 13:55:05 +0200
From: Pavel Machek <pavel@....cz>
To: Erick Karanja <karanja99erick@...il.com>
Cc: perex@...ex.cz, tiwai@...e.com, linux-sound@...r.kernel.org,
	linux-kernel@...r.kernel.org, julia.lawall@...ia.fr
Subject: Re: [PATCH] staging: sound: Adjust mutex unlock order

On Wed 2025-07-16 09:23:30, Erick Karanja wrote:
> The mutexes qdev_mutex and chip->mutex are acquired in that order
> throughout the driver. To preserve proper lock hierarchy and avoid
> potential deadlocks, they must be released in the reverse order
> of acquisition.

Please explain how the deadlock would happen.

								Pavel
-- 
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, and Musk!

Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)