diff options
| author | Takashi Iwai <tiwai@suse.de> | 2018-04-07 11:48:58 +0200 |
|---|---|---|
| committer | Takashi Iwai <tiwai@suse.de> | 2018-04-07 13:10:11 +0200 |
| commit | e15dc99dbb9cf99f6432e8e3c0b3a8f7a3403a86 (patch) | |
| tree | b799a26d325c9cf18c19829c999b39ac8f7097ee /security/integrity | |
| parent | b580fbfff13b01fa79a0760cbb6386f33bc9e10b (diff) | |
| download | linux-e15dc99dbb9cf99f6432e8e3c0b3a8f7a3403a86.tar.bz2 | |
ALSA: pcm: Fix endless loop for XRUN recovery in OSS emulation
The commit 02a5d6925cd3 ("ALSA: pcm: Avoid potential races between OSS
ioctls and read/write") split the PCM preparation code to a locked
version, and it added a sanity check of runtime->oss.prepare flag
along with the change. This leaded to an endless loop when the stream
gets XRUN: namely, snd_pcm_oss_write3() and co call
snd_pcm_oss_prepare() without setting runtime->oss.prepare flag and
the loop continues until the PCM state reaches to another one.
As the function is supposed to execute the preparation
unconditionally, drop the invalid state check there.
The bug was triggered by syzkaller.
Fixes: 02a5d6925cd3 ("ALSA: pcm: Avoid potential races between OSS ioctls and read/write")
Reported-by: syzbot+150189c103427d31a053@syzkaller.appspotmail.com
Reported-by: syzbot+7e3f31a52646f939c052@syzkaller.appspotmail.com
Reported-by: syzbot+4f2016cf5185da7759dc@syzkaller.appspotmail.com
Cc: <stable@vger.kernel.org>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'security/integrity')
0 files changed, 0 insertions, 0 deletions