diff options
| author | Hans Verkuil <hverkuil@xs4all.nl> | 2019-01-11 07:07:25 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-09-16 08:22:02 +0200 |
| commit | 424b75b79994c57a87e34ff1a0fd462dd3dbcb24 (patch) | |
| tree | f60e0b64821b29df1b07d9b70cbae01111e3dd93 /arch/arc | |
| parent | be77686f0369dff64d7cce4b56dcce4559421ad6 (diff) | |
| download | linux-stable-424b75b79994c57a87e34ff1a0fd462dd3dbcb24.tar.gz linux-stable-424b75b79994c57a87e34ff1a0fd462dd3dbcb24.tar.bz2 linux-stable-424b75b79994c57a87e34ff1a0fd462dd3dbcb24.zip | |
media: vim2m: only cancel work if it is for right context
[ Upstream commit 240809ef6630a4ce57c273c2d79ffb657cd361eb ]
cancel_delayed_work_sync() was called for any queue, but it should only
be called for the queue that is associated with the currently running job.
Otherwise, if two filehandles are streaming at the same time, then closing the
first will cancel the work which might still be running for a job from the
second filehandle. As a result the second filehandle will never be able to
finish the job and an attempt to stop streaming on that second filehandle will
stall.
Fixes: 52117be68b82 ("media: vim2m: use cancel_delayed_work_sync instead of flush_schedule_work")
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: <stable@vger.kernel.org> # for v4.20 and up
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'arch/arc')
0 files changed, 0 insertions, 0 deletions