public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Koba Ko <koba.ko@canonical.com>, Vinod Koul <vkoul@kernel.org>,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] dmaengine: Fix client_count is countered one more incorrectly.
Date: Fri, 16 Sep 2022 08:46:08 -0700	[thread overview]
Message-ID: <262e809d-21e8-99ee-2245-5c28fa98afe1@intel.com> (raw)
In-Reply-To: <20220830093207.951704-1-koba.ko@canonical.com>


On 8/30/2022 2:32 AM, Koba Ko wrote:
> If the passed client_count is 0,
> it would be incremented by balance_ref_count first
> then increment one more.
> This would cause client_count to 2.
>
> cat /sys/class/dma/dma0chan*/in_use
> 2
> 2
> 2
>
> Fixes: d2f4f99db3e9 ("dmaengine: Rework dma_chan_get")
> Signed-off-by: Koba Ko <koba.ko@canonical.com>

Reviewed-by: Dave Jiang <dave.jiang@intel.com>


> ---
>   drivers/dma/dmaengine.c | 7 ++++---
>   1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/dma/dmaengine.c b/drivers/dma/dmaengine.c
> index 2cfa8458b51be..78f8a9f3ad825 100644
> --- a/drivers/dma/dmaengine.c
> +++ b/drivers/dma/dmaengine.c
> @@ -451,7 +451,8 @@ static int dma_chan_get(struct dma_chan *chan)
>   	/* The channel is already in use, update client count */
>   	if (chan->client_count) {
>   		__module_get(owner);
> -		goto out;
> +		chan->client_count++;
> +		return 0;
>   	}
>   
>   	if (!try_module_get(owner))
> @@ -470,11 +471,11 @@ static int dma_chan_get(struct dma_chan *chan)
>   			goto err_out;
>   	}
>   
> +	chan->client_count++;
> +
>   	if (!dma_has_cap(DMA_PRIVATE, chan->device->cap_mask))
>   		balance_ref_count(chan);
>   
> -out:
> -	chan->client_count++;
>   	return 0;
>   
>   err_out:

  parent reply	other threads:[~2022-09-16 15:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30  9:32 [PATCH 3/3] dmaengine: Fix client_count is countered one more incorrectly Koba Ko
2022-09-02  7:13 ` Jie Hai
2022-09-16 15:33 ` Jerry Snitselaar
2022-09-16 15:46 ` Dave Jiang [this message]
2022-09-29 16:57 ` Jerry Snitselaar
2022-09-29 17:10   ` Vinod Koul
2022-09-29 17:26     ` Jerry Snitselaar
2022-09-30  4:44       ` Koba Ko
2022-09-30  5:56         ` Jerry Snitselaar
2022-09-30  6:25           ` Koba Ko
2022-09-30 16:17             ` 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=262e809d-21e8-99ee-2245-5c28fa98afe1@intel.com \
    --to=dave.jiang@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=koba.ko@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vkoul@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