]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
ALSA: seq: Don't break snd_use_lock_sync() loop by timeout
authorTakashi Iwai <tiwai@suse.de>
Sun, 9 Apr 2017 08:41:27 +0000 (10:41 +0200)
committerJiri Slaby <jslaby@suse.cz>
Tue, 9 May 2017 06:19:53 +0000 (08:19 +0200)
commit47da45deafcf8f83a93c81558e2b60486e14b0de
tree435c3d10aba1e06f8ee0786ab81565c64f521cc5
parent97254930bc706c411f49084a7fc30123ab9fb099
ALSA: seq: Don't break snd_use_lock_sync() loop by timeout

commit 4e7655fd4f47c23e5249ea260dc802f909a64611 upstream.

The snd_use_lock_sync() (thus its implementation
snd_use_lock_sync_helper()) has the 5 seconds timeout to break out of
the sync loop.  It was introduced from the beginning, just to be
"safer", in terms of avoiding the stupid bugs.

However, as Ben Hutchings suggested, this timeout rather introduces a
potential leak or use-after-free that was apparently fixed by the
commit 2d7d54002e39 ("ALSA: seq: Fix race during FIFO resize"):
for example, snd_seq_fifo_event_in() -> snd_seq_event_dup() ->
copy_from_user() could block for a long time, and snd_use_lock_sync()
goes timeout and still leaves the cell at releasing the pool.

For fixing such a problem, we remove the break by the timeout while
still keeping the warning.

Suggested-by: Ben Hutchings <ben.hutchings@codethink.co.uk>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
sound/core/seq/seq_lock.c