[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <56766037-972e-9e5b-74c1-88633a72a77f@gmail.com>
Date: Sat, 29 Jan 2022 11:33:26 +0800
From: Jia-Ju Bai <baijiaju1990@...il.com>
To: perex@...ex.cz, tiwai@...e.com, broonie@...nel.org,
o-takashi@...amocchi.jp
Cc: alsa-devel@...a-project.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: [BUG] ALSA: core: possible deadlock involving waiting and locking
operations
Hello,
My static analysis tool reports a possible deadlock in the sound driver
in Linux 5.10:
snd_card_disconnect_sync()
spin_lock_irq(&card->files_lock); --> Line 461 (Lock A)
wait_event_lock_irq(card->remove_sleep, ...); --> Line 462 (Wait X)
spin_unlock_irq(&card->files_lock); --> Line 465 (Unlock A)
snd_hwdep_release()
mutex_lock(&hw->open_mutex); --> Line 152 (Lock B)
mutex_unlock(&hw->open_mutex); --> Line 157 (Unlock B)
snd_card_file_remove()
wake_up_all(&card->remove_sleep); --> Line 976 (Wake X)
snd_hwdep_open()
mutex_lock(&hw->open_mutex); --> Line 95 (Lock B)
snd_card_file_add()
spin_lock(&card->files_lock); --> Line 932 (Lock A)
spin_unlock(&card->files_lock); --> Line 940 (Unlock A)
mutex_unlock(&hw->open_mutex); --> Line 139 (Unlock B)
When snd_card_disconnect_sync() is executed, "Wait X" is performed by
holding "Lock A". If snd_hwdep_open() is executed at this time, it holds
"Lock B" and then waits for acquiring "Lock A". If snd_hwdep_release()
is executed at this time, it waits for acquiring "Lock B", and thus
"Wake X" cannot be performed to wake up "Wait X" in
snd_card_disconnect_sync(), causing a possible deadlock.
I am not quite sure whether this possible problem is real and how to fix
it if it is real.
Any feedback would be appreciated, thanks :)
Best wishes,
Jia-Ju Bai
Powered by blists - more mailing lists