aboutsummaryrefslogtreecommitdiffstats
path: root/sound/Kconfig
diff options
context:
space:
mode:
authorTakashi Iwai <tiwai@suse.de>2016-04-14 18:02:37 +0200
committerAndreas Blaesius <skate4life@gmx.de>2017-03-17 11:03:02 +0100
commit19920e2d711b3705b45205e866aa886359121ba6 (patch)
tree710a5f46d9fe7489613c86348f5d6d5b5717c015 /sound/Kconfig
parent55ac77ef05bb2fe6db6183823366fcd2e63582db (diff)
downloadkernel_samsung_espresso10-19920e2d711b3705b45205e866aa886359121ba6.zip
kernel_samsung_espresso10-19920e2d711b3705b45205e866aa886359121ba6.tar.gz
kernel_samsung_espresso10-19920e2d711b3705b45205e866aa886359121ba6.tar.bz2
ALSA: pcm : Call kill_fasync() in stream lock
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. Change-Id: Iaebf87120a34e16bd0b259b2cf661aad6b2cc388 Reported-by: Baozeng Ding <sploving1@gmail.com> Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'sound/Kconfig')
0 files changed, 0 insertions, 0 deletions