From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Alexandre Courbot <acourbot@chromium.org>,
Andrzej Pietrasiewicz <andrzej.p@samsung.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [media] s5p-jpeg: fix recursive spinlock acquisition
Date: Tue, 25 Apr 2017 21:15:15 +0200 [thread overview]
Message-ID: <14d0d257-a5c3-222e-137d-4991482c6fb4@gmail.com> (raw)
In-Reply-To: <20170425061943.717-1-acourbot@chromium.org>
Hi Alexandre,
Thanks for the patch.
On 04/25/2017 08:19 AM, Alexandre Courbot wrote:
> v4l2_m2m_job_finish(), which is called from the interrupt handler with
> slock acquired, can call the device_run() hook immediately if another
> context was in the queue. This hook also acquires slock, resulting in
> a deadlock for this scenario.
>
> Fix this by releasing slock right before calling v4l2_m2m_job_finish().
> This is safe to do as the state of the hardware cannot change before
> v4l2_m2m_job_finish() is called anyway.
>
> Signed-off-by: Alexandre Courbot <acourbot@chromium.org>
> ---
> drivers/media/platform/s5p-jpeg/jpeg-core.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/media/platform/s5p-jpeg/jpeg-core.c b/drivers/media/platform/s5p-jpeg/jpeg-core.c
> index 52dc7941db65..223b4379929e 100644
> --- a/drivers/media/platform/s5p-jpeg/jpeg-core.c
> +++ b/drivers/media/platform/s5p-jpeg/jpeg-core.c
> @@ -2642,13 +2642,13 @@ static irqreturn_t s5p_jpeg_irq(int irq, void *dev_id)
> if (curr_ctx->mode == S5P_JPEG_ENCODE)
> vb2_set_plane_payload(&dst_buf->vb2_buf, 0, payload_size);
> v4l2_m2m_buf_done(dst_buf, state);
> - v4l2_m2m_job_finish(jpeg->m2m_dev, curr_ctx->fh.m2m_ctx);
>
> curr_ctx->subsampling = s5p_jpeg_get_subsampling_mode(jpeg->regs);
> spin_unlock(&jpeg->slock);
>
> s5p_jpeg_clear_int(jpeg->regs);
>
> + v4l2_m2m_job_finish(jpeg->m2m_dev, curr_ctx->fh.m2m_ctx);
> return IRQ_HANDLED;
> }
>
> @@ -2707,11 +2707,12 @@ static irqreturn_t exynos4_jpeg_irq(int irq, void *priv)
> v4l2_m2m_buf_done(dst_vb, VB2_BUF_STATE_ERROR);
> }
>
> - v4l2_m2m_job_finish(jpeg->m2m_dev, curr_ctx->fh.m2m_ctx);
> if (jpeg->variant->version == SJPEG_EXYNOS4)
> curr_ctx->subsampling = exynos4_jpeg_get_frame_fmt(jpeg->regs);
>
> spin_unlock(&jpeg->slock);
> +
> + v4l2_m2m_job_finish(jpeg->m2m_dev, curr_ctx->fh.m2m_ctx);
> return IRQ_HANDLED;
> }
>
> @@ -2770,10 +2771,15 @@ static irqreturn_t exynos3250_jpeg_irq(int irq, void *dev_id)
> if (curr_ctx->mode == S5P_JPEG_ENCODE)
> vb2_set_plane_payload(&dst_buf->vb2_buf, 0, payload_size);
> v4l2_m2m_buf_done(dst_buf, state);
> - v4l2_m2m_job_finish(jpeg->m2m_dev, curr_ctx->fh.m2m_ctx);
>
> curr_ctx->subsampling =
> exynos3250_jpeg_get_subsampling_mode(jpeg->regs);
> +
> + spin_unlock(&jpeg->slock);
> +
> + v4l2_m2m_job_finish(jpeg->m2m_dev, curr_ctx->fh.m2m_ctx);
> + return IRQ_HANDLED;
> +
> exit_unlock:
> spin_unlock(&jpeg->slock);
> return IRQ_HANDLED;
>
Acked-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Just out of curiosity - could you share how you discovered the problem -
by some static checkers or trying to use the driver?
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2017-04-25 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 6:19 Alexandre Courbot
2017-04-25 19:15 ` Jacek Anaszewski [this message]
2017-04-26 2:54 ` Alexandre Courbot
2017-04-26 19:35 ` Jacek Anaszewski
2017-05-29 7:29 ` Alexandre Courbot
2017-05-29 19:08 ` Jacek Anaszewski
[not found] ` <CGME20170530083004epcas1p22ffe80b6a9442bcd3a6fb0b02381759f@epcas1p2.samsung.com>
2017-05-30 8:30 ` Sylwester Nawrocki
2017-05-30 8:50 ` Alexandre Courbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14d0d257-a5c3-222e-137d-4991482c6fb4@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=acourbot@chromium.org \
--cc=andrzej.p@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®