Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp3772223pxt; Tue, 10 Aug 2021 10:58:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyRUYR0db9brptCZm9InGAtrPBJcPE25vzvXSVIp9lQ7Hq5t7YQH7Ebn0Kvy3Lncs6k1puT X-Received: by 2002:a6b:7309:: with SMTP id e9mr62891ioh.183.1628618334714; Tue, 10 Aug 2021 10:58:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628618334; cv=none; d=google.com; s=arc-20160816; b=LTcgO3Anbgy06eAW5ds7oVGmMJY7VkMpLim1TLDwlS2PE0N6qBCTADQCRuq0LmXgTB h05GF5sAQXqpp3Avdfo6DhBIOTMX2/2lvqbF4f/uDNRjPPGGbbu3OlUeI4eNIYlXBcE3 AqFDxJMfp6bG6sUqRk5uhhuv9ukIzgtmXc43cOwnSZDAV68mFKzFD//hyg/9cFxLUdT6 DrDFrR0ARM5IMXBgCj8BooZapYMDKU7VOUStLPrsAfXt3Dv0RM+hoa4BCRs6mOtWHsZI XXbNen0YyFJgMTwnrHQH1a7a4DIswsfwbLIBcre8dXqG29wAUDs9frT/ckwvu+EuDlul E0zA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=jJd16lbOAevM0otQL2y5WbAaUTROMuv5ECMPS97KlfM=; b=JfSLqeBDx7w468zcs6F0Vw4SDiS66Rgnz//6drn40vpKMp3e1WeKGhqlygPzCQ8Oru 4wXIzLSqatL14KpnQKhJqqJIw9ctgcaX3OMXWjfxiYpaKDBvd7SVe33wtZ5Eu0qFhL7N 4tUSIiySRBxLgdbsBqLp7jAbs5xmpvQJ7R3GI5HrhGS897Td1IMLXASUrpfMOArgioR3 jKtaQrR14HptxEC7jbiErZN0Hm4WTiD47Ppsd36EatdiqJ8d765lz+Ht305xFAPaNSM5 5V95g1VfgPCOZQ4zfjIoJxs8W72S6KbDjvUlzMJqjUfR8DssXzDRe6Lq+jWxwXoJJ0G5 7n3w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Ysgc7HRK; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v20si22673411jas.98.2021.08.10.10.58.40; Tue, 10 Aug 2021 10:58:54 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Ysgc7HRK; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236434AbhHJR5H (ORCPT + 99 others); Tue, 10 Aug 2021 13:57:07 -0400 Received: from mail.kernel.org ([198.145.29.99]:50372 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236998AbhHJRyN (ORCPT ); Tue, 10 Aug 2021 13:54:13 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 746B961371; Tue, 10 Aug 2021 17:44:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1628617448; bh=76zOx8RR5kNg3eS8gh3KAjbFpnzDu9itDLeMLvoYuqo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Ysgc7HRKPXBe1uzOVJ0fdIldjMUXJjc98ReahtVaU7f7+8u/CNb8tPPhF1/q/ONm3 cVKSx6RQjmOVBdgGViVD6Z6pnOfxLF2gkHbLvjiYyq+BO2UEpZP80MYaJkxL0sbfhH Hgj79gnzn438JfMwK+jrDtqnmLZ1R8jbDf2WM2tU= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Zhang Qilong , Vinod Koul , Sasha Levin Subject: [PATCH 5.13 030/175] dmaengine: stm32-dmamux: Fix PM usage counter unbalance in stm32 dmamux ops Date: Tue, 10 Aug 2021 19:28:58 +0200 Message-Id: <20210810173001.948045507@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210810173000.928681411@linuxfoundation.org> References: <20210810173000.928681411@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Zhang Qilong [ Upstream commit baa16371c9525f24d508508e4d296c031e1de29c ] pm_runtime_get_sync will increment pm usage counter even it failed. Forgetting to putting operation will result in reference leak here. We fix it by replacing it with pm_runtime_resume_and_get to keep usage counter balanced. Fixes: 4f3ceca254e0f ("dmaengine: stm32-dmamux: Add PM Runtime support") Signed-off-by: Zhang Qilong Link: https://lore.kernel.org/r/20210607064640.121394-3-zhangqilong3@huawei.com Signed-off-by: Vinod Koul Signed-off-by: Sasha Levin --- drivers/dma/stm32-dmamux.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/dma/stm32-dmamux.c b/drivers/dma/stm32-dmamux.c index ef0d0555103d..a42164389ebc 100644 --- a/drivers/dma/stm32-dmamux.c +++ b/drivers/dma/stm32-dmamux.c @@ -137,7 +137,7 @@ static void *stm32_dmamux_route_allocate(struct of_phandle_args *dma_spec, /* Set dma request */ spin_lock_irqsave(&dmamux->lock, flags); - ret = pm_runtime_get_sync(&pdev->dev); + ret = pm_runtime_resume_and_get(&pdev->dev); if (ret < 0) { spin_unlock_irqrestore(&dmamux->lock, flags); goto error; @@ -336,7 +336,7 @@ static int stm32_dmamux_suspend(struct device *dev) struct stm32_dmamux_data *stm32_dmamux = platform_get_drvdata(pdev); int i, ret; - ret = pm_runtime_get_sync(dev); + ret = pm_runtime_resume_and_get(dev); if (ret < 0) return ret; @@ -361,7 +361,7 @@ static int stm32_dmamux_resume(struct device *dev) if (ret < 0) return ret; - ret = pm_runtime_get_sync(dev); + ret = pm_runtime_resume_and_get(dev); if (ret < 0) return ret; -- 2.30.2