diff options
author | Takashi Iwai <tiwai@suse.de> | 2019-10-30 22:42:57 +0100 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-11-06 12:43:41 +0100 |
commit | 1ff779c530064839511d5b327cd2ade7a17a2651 (patch) | |
tree | 695b2bb68f1d448272ad95f49a1418b97019c7d9 /MAINTAINERS | |
parent | b617db2ebf29bc60768df01a831d79582630ee8a (diff) | |
download | linux-stable-1ff779c530064839511d5b327cd2ade7a17a2651.tar.gz linux-stable-1ff779c530064839511d5b327cd2ade7a17a2651.tar.bz2 linux-stable-1ff779c530064839511d5b327cd2ade7a17a2651.zip |
ALSA: timer: Fix mutex deadlock at releasing card
[ Upstream commit a39331867335d4a94b6165e306265c9e24aca073 ]
When a card is disconnected while in use, the system waits until all
opened files are closed then releases the card. This is done via
put_device() of the card device in each device release code.
The recently reported mutex deadlock bug happens in this code path;
snd_timer_close() for the timer device deals with the global
register_mutex and it calls put_device() there. When this timer
device is the last one, the card gets freed and it eventually calls
snd_timer_free(), which has again the protection with the global
register_mutex -- boom.
Basically put_device() call itself is race-free, so a relative simple
workaround is to move this put_device() call out of the mutex. For
achieving that, in this patch, snd_timer_close_locked() got a new
argument to store the card device pointer in return, and each caller
invokes put_device() with the returned object after the mutex unlock.
Reported-and-tested-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions