summaryrefslogtreecommitdiff
path: root/mm/cleancache.c
diff options
context:
space:
mode:
authorTakashi Iwai <tiwai@suse.de>2022-03-22 20:07:18 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2022-03-28 10:57:09 +0300
commit8527c8f052fb42091c6569cb928e472376a4a889 (patch)
tree9695bdf2e403a7369aa6f333e3901319718b551b /mm/cleancache.c
parent0f6947f5f5208f6ebd4d76a82a4757e2839a23f8 (diff)
downloadlinux-8527c8f052fb42091c6569cb928e472376a4a889.tar.xz
ALSA: pcm: Fix races among concurrent read/write and buffer changes
commit dca947d4d26dbf925a64a6cfb2ddbc035e831a3d upstream. In the current PCM design, the read/write syscalls (as well as the equivalent ioctls) are allowed before the PCM stream is running, that is, at PCM PREPARED state. Meanwhile, we also allow to re-issue hw_params and hw_free ioctl calls at the PREPARED state that may change or free the buffers, too. The problem is that there is no protection against those mix-ups. This patch applies the previously introduced runtime->buffer_mutex to the read/write operations so that the concurrent hw_params or hw_free call can no longer interfere during the operation. The mutex is unlocked before scheduling, so we don't take it too long. Cc: <stable@vger.kernel.org> Reviewed-by: Jaroslav Kysela <perex@perex.cz> Link: https://lore.kernel.org/r/20220322170720.3529-3-tiwai@suse.de Signed-off-by: Takashi Iwai <tiwai@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm/cleancache.c')
0 files changed, 0 insertions, 0 deletions