From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] dmaengine: shdma: fix a race condition in __ld_cleanup()
Date: Sat, 11 Oct 2014 17:27:52 +0000 [thread overview]
Message-ID: <1802219.jBtroDoh4E@avalon> (raw)
In-Reply-To: <1412820540-4892-1-git-send-email-yoshihiro.shimoda.uh@renesas.com>
Hi Shimoda-san,
On Thursday 09 October 2014 11:09:00 Yoshihiro Shimoda wrote:
> This patch fixes a race condition about a list of shdma-base driver.
> If we don't apply this patch, a dma slave driver (especially a usb
> peripheral driver) may not be able to start the transfer.
>
> If a dma slave driver has a callback, __ld_cleanup() will call
> the callback before this driver removes the list. After the callback,
> since the return value of __ld_cleanup() is not zero,
> shdma_chan_ld_cleanup() calls __ld_cleanup() again. And, __ld_clean()
> will removes the list.
>
> At this time, if a dma slave driver calls dmaengine_submit() before
> this driver removes the list, this driver will set schan->pm_state
> to SHDMA_PM_PENDING in shdma_tx_submit(). And then, even if a dma
> slave driver calls dma_async_issue_pending(), this driver don't
> start the transfer because the schan->pm_state is SHDMA_PM_PENDING
> in shdma_issue_pending().
>
> So, this patch adds a new condition in __ld_clean() to check if the
> schan->pm_state is SHDMA_PM_PENDING or not.
>
> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
This looks good to me, but given the complexity of the shdma-base code it's
very difficult to make sure there will be no undesired side effect. I don't
have any issue with the patch, but I can't ack it either.
> ---
> This patch is based on slave-dma.git / next branch.
> (commit id : ade4a2a8e6e40fe18be1f83e5ea2e915692a0028)
>
> drivers/dma/sh/shdma-base.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/dma/sh/shdma-base.c b/drivers/dma/sh/shdma-base.c
> index 42d4974..2fd2f0ea 100644
> --- a/drivers/dma/sh/shdma-base.c
> +++ b/drivers/dma/sh/shdma-base.c
> @@ -391,6 +391,8 @@ static dma_async_tx_callback __ld_cleanup(struct
> shdma_chan *schan, bool all) dev_dbg(schan->dev, "Bring down channel %d\n",
> schan->id);
> pm_runtime_put(schan->dev);
> schan->pm_state = SHDMA_PM_ESTABLISHED;
> + } else if (schan->pm_state = SHDMA_PM_PENDING) {
> + shdma_chan_xfer_ld_queue(schan);
> }
> }
> }
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-10-11 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 2:09 [PATCH] dmaengine: shdma: fix a race condition in __ld_cleanup() Yoshihiro Shimoda
2014-10-11 17:27 ` Laurent Pinchart [this message]
2014-11-12 10:56 ` Vinod Koul
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=1802219.jBtroDoh4E@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.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