diff options
author | Takashi Iwai <tiwai@suse.de> | 2018-01-04 17:38:54 +0100 |
---|---|---|
committer | Takashi Iwai <tiwai@suse.de> | 2018-01-05 16:44:16 +0100 |
commit | 898dfe4687f460ba337a01c11549f87269a13fa2 (patch) | |
tree | a62adb7385d61ac2e651abe1ec806f2c0899ec32 /sound/arm | |
parent | b088b53e20c7d09b5ab84c5688e609f478e5c417 (diff) | |
download | linux-898dfe4687f460ba337a01c11549f87269a13fa2.tar.bz2 |
ALSA: aloop: Fix racy hw constraints adjustment
The aloop driver tries to update the hw constraints of the connected
target on the cable of the opened PCM substream. This is done by
adding the extra hw constraints rules referring to the substream
runtime->hw fields, while the other substream may update the runtime
hw of another side on the fly.
This is, however, racy and may result in the inconsistent values when
both PCM streams perform the prepare concurrently. One of the reason
is that it overwrites the other's runtime->hw field; which is not only
racy but also broken when it's called before the open of another side
finishes. And, since the reference to runtime->hw isn't protected,
the concurrent write may give the partial value update and become
inconsistent.
This patch is an attempt to fix and clean up:
- The prepare doesn't change the runtime->hw of other side any longer,
but only update the cable->hw that is referred commonly.
- The extra rules refer to the loopback_pcm object instead of the
runtime->hw. The actual hw is deduced from cable->hw.
- The extra rules take the cable_lock to protect against the race.
Fixes: b1c73fc8e697 ("ALSA: snd-aloop: Fix hw_params restrictions and checking")
Cc: <stable@vger.kernel.org>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'sound/arm')
0 files changed, 0 insertions, 0 deletions