diff options
| author | Takashi Iwai <tiwai@suse.de> | 2016-12-12 17:33:06 +0100 |
|---|---|---|
| committer | Richard Chang <dickchang@google.com> | 2017-04-11 11:40:42 -0700 |
| commit | 48bbed52c64fd68c1d071f0ab0ce1473320ddbca (patch) | |
| tree | 985ce94d26c91998dddd5ee3bc7a1c7820ae55a0 /net/lapb/lapb_timer.c | |
| parent | a0f52cfc14a9d527515b4f857df9e865d1dc2e42 (diff) | |
ALSA: pcm : Call kill_fasync() in stream lock
commit 3aa02cb664c5fb1042958c8d1aa8c35055a2ebc4 upstream.
Currently kill_fasync() is called outside the stream lock in
snd_pcm_period_elapsed(). This is potentially racy, since the stream
may get released even during the irq handler is running. Although
snd_pcm_release_substream() calls snd_pcm_drop(), this doesn't
guarantee that the irq handler finishes, thus the kill_fasync() call
outside the stream spin lock may be invoked after the substream is
detached, as recently reported by KASAN.
As a quick workaround, move kill_fasync() call inside the stream
lock. The fasync is rarely used interface, so this shouldn't have a
big impact from the performance POV.
Ideally, we should implement some sync mechanism for the proper finish
of stream and irq handler. But this oneliner should suffice for most
cases, so far.
Reported-by: Baozeng Ding <sploving1@gmail.com>
Bug: 34068036
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Willy Tarreau <w@1wt.eu>
Change-Id: Idd6a2de99d82699cc4f7cb619bf03566a10730ce
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions
