From: Takashi Iwai <tiwai@suse.de>
To: "Cássio Gabriel" <cassiogabrielcontato@gmail.com>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda: intel: Drop obsolete probe-work unlock workaround
Date: Sun, 29 Mar 2026 11:07:43 +0200 [thread overview]
Message-ID: <878qbbuhpc.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260328-hda-intel-drop-obsolete-probe-workaround-v1-1-bc43aeafc98b@gmail.com>
On Sun, 29 Mar 2026 00:42:01 +0100,
Cássio Gabriel wrote:
>
> Commit ab949d519601 ("ALSA: hda - Fix deadlock of controller device
> lock at unbinding") added a temporary device_unlock()/device_lock()
> pair around probe-work cancellation to avoid a deadlock between
> controller unbind and codec probe.
>
> That deadlock depended on the driver core taking both a device lock and
> its parent lock during bind and unbind. Since commit 8c97a46af04b
> ("driver core: hold dev's parent lock when needed") and follow-up
> fixes, the parent lock is only taken when bus->need_parent_lock is set.
> The HDA bus does not set that flag, so codec binding no longer locks
> the controller device as the codec's parent.
>
> Keep cancel_delayed_work_sync(), since the async probe/remove race
> still needs to be serialized, but drop the stale unlock/relock
> workaround and its outdated FIXME comment. Keeping it around only
> opens an unnecessary unlocked window inside azx_remove().
>
> Signed-off-by: Cássio Gabriel <cassiogabrielcontato@gmail.com>
A good catch. Applied to for-next branch now.
thanks,
Takashi
prev parent reply other threads:[~2026-03-29 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 23:42 [PATCH] ALSA: hda: intel: Drop obsolete probe-work unlock workaround Cássio Gabriel
2026-03-29 9:07 ` Takashi Iwai [this message]
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=878qbbuhpc.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=cassiogabrielcontato@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.