media: staging: rkisp1: cap: protect buf.curr and buf.next with buf.lock
authorDafna Hirschfeld <dafna.hirschfeld@collabora.com>
Tue, 14 Jul 2020 12:38:30 +0000 (14:38 +0200)
committerMauro Carvalho Chehab <mchehab+huawei@kernel.org>
Sun, 19 Jul 2020 12:04:34 +0000 (14:04 +0200)
commit454748e3b3529218a50920e643dab6f149ab2639
treef071b3d51d649a65f803e00b7045773a8d573e81
parentaa86e0bbf2ee3fe338798af78f02b5e6088b50c1
media: staging: rkisp1: cap: protect buf.curr and buf.next with buf.lock

The spinlock buf.lock should protect access to the buffers.
This includes the buffers in buf.queue and also buf.curr and
buf.next. The function 'rkisp1_set_next_buf' access buf.next
therefore it should also be protected with the lock.

Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
Acked-by: Helen Koike <helen.koike@collabora.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
drivers/staging/media/rkisp1/rkisp1-capture.c