From: Takashi Iwai <tiwai@suse.de>
To: Erick Karanja <karanja99erick@gmail.com>
Cc: perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] ALSA: usb-audio: qcom: Adjust mutex unlock order
Date: Tue, 22 Jul 2025 11:38:50 +0200 [thread overview]
Message-ID: <87ms8wo991.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250721114554.1666104-1-karanja99erick@gmail.com>
On Mon, 21 Jul 2025 13:45:53 +0200,
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.
>
> This change reorders the unlock sequence to first release chip->mutex
> followed by qdev_mutex, ensuring consistency with the locking pattern.
>
> Fixes: 326bbc348298a ("ALSA: usb-audio: qcom: Introduce QC USB
> SND offloading support")
This has to be a single line without folding.
> changes since v3:
> - Add the correct fixes tag.
>
> Signed-off-by: Erick Karanja <karanja99erick@gmail.com>
> ---
> sound/usb/qcom/qc_audio_offload.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/sound/usb/qcom/qc_audio_offload.c b/sound/usb/qcom/qc_audio_offload.c
> index 3543b5a53592..711f5612a83a 100644
> --- a/sound/usb/qcom/qc_audio_offload.c
> +++ b/sound/usb/qcom/qc_audio_offload.c
> @@ -825,8 +825,8 @@ static int uaudio_sideband_notifier(struct usb_interface *intf,
> }
> }
>
> - mutex_unlock(&qdev_mutex);
> mutex_unlock(&chip->mutex);
> + mutex_unlock(&qdev_mutex);
>
> return 0;
> }
> @@ -1865,8 +1865,8 @@ static void qc_usb_audio_offload_disconnect(struct snd_usb_audio *chip)
>
> /* Device has already been cleaned up, or never populated */
> if (!dev->chip) {
> - mutex_unlock(&qdev_mutex);
> mutex_unlock(&chip->mutex);
> + mutex_unlock(&qdev_mutex);
> return;
> }
>
> @@ -1921,8 +1921,8 @@ static void qc_usb_audio_offload_suspend(struct usb_interface *intf,
>
> uaudio_send_disconnect_ind(chip);
>
> + mutex_unlock(&chip->mutex);
> mutex_unlock(&qdev_mutex);
> - mutex_unlock(&chip->mutex);
The above used spaces instead of tabs, and I corrected in my side.
Such a failure could be spotted out by running scripts/checkpatch.pl.
At the next time, please run and test it before submissions.
In anyway, I applied the patch now.
thanks,
Takashi
next prev parent reply other threads:[~2025-07-22 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 11:45 [PATCH v4] ALSA: usb-audio: qcom: Adjust mutex unlock order Erick Karanja
2025-07-21 14:06 ` Markus Elfring
2025-07-21 15:00 ` Markus Elfring
2025-07-22 9:38 ` Takashi Iwai [this message]
2025-07-22 19:22 ` Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ms8wo991.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=karanja99erick@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox