Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp1876933ybg; Thu, 4 Jun 2020 23:15:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx9y3fAOK2HoRuLPqpTmUtm29GM7qCFjG4KvwKIzlvxHwiWsfSyYs7ouBAtI7y4gGr0xNON X-Received: by 2002:a17:906:509:: with SMTP id j9mr6899183eja.341.1591337754858; Thu, 04 Jun 2020 23:15:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591337754; cv=none; d=google.com; s=arc-20160816; b=zp1Xs3t6nrRN7zLhnqPUevuzOPrEbfQJ0Hc3ZIyqsf60b1wVuEGzCjYp7I3XEVXK/d PXMqeodtbcEKHPoTJ9Ii5Ajya0jYh+jhckwWinUGt5YVZNv5zanTD5AqY+rm8UpWaF1F dMEH2WTsPdPAi4/j+vIf2lCu8PG8vTvXy+3R2rcryVb2Vckk10dJbx6eEWSCNTmf5XW/ Dnu933ed08GOGW/FxOx9aO/cHoRSrwzKP3MRk2Sij8W8JayqFhsUVpF012DjWUTgXWIW bBNERq1KHqKTQR5vLbcQ1IvkRfIXxK5zYAP4LtEe1bP1tj9W803bXLI9FqYLDeyfOBEb cv8g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=1DliN9cWI9tOr6qCWIwnsIRGllVyzqzKKx/V7aOAhqw=; b=bNXcCmbxbuUyglal6ca9MRMGLwb4IPNGHbYfgwB5SidOztcC+xrui92CZ8TEEfVGDh FKJnuIer39fKGO2+lfCrKO7BpbhM4F6FHUAZNldkuxCbyuR5bOlAatgBvccySQ4qb8um JOau3+LTwj334M+6aNex+whobKXStG+0kdndhBg7IMSMv/PJZNCDliWSDNRlDfH0EsKC xb10iXauiy1xfXwfWkLZJIK9vVVi+8sJjospV+eaNh7LY5JM1G653lZDnoZ5abzAi76n VWlMQdj1Mq4/h/jB9u3biChN4OC51093vojamLYR75jzzKCEpiTW9R+ALTirRUCssTBe zUuA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=kLPvCJog; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v1si3248454ejd.509.2020.06.04.23.15.31; Thu, 04 Jun 2020 23:15: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=@gmail.com header.s=20161025 header.b=kLPvCJog; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726072AbgFEGNs (ORCPT + 99 others); Fri, 5 Jun 2020 02:13:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57906 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725962AbgFEGNr (ORCPT ); Fri, 5 Jun 2020 02:13:47 -0400 Received: from mail-io1-xd44.google.com (mail-io1-xd44.google.com [IPv6:2607:f8b0:4864:20::d44]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A7E83C08C5C2; Thu, 4 Jun 2020 23:13:47 -0700 (PDT) Received: by mail-io1-xd44.google.com with SMTP id q8so9028418iow.7; Thu, 04 Jun 2020 23:13:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1DliN9cWI9tOr6qCWIwnsIRGllVyzqzKKx/V7aOAhqw=; b=kLPvCJogKo7qETqtMQGB6/ogTb+8DdxAWtZblbO2zztSbESn5CXEbgj7hJpt3Zfe2U 6Y5/4wYylXCZl1jWxmzm05PBz1nqCf/Cets7bwLMU+Tj8nC6KRayOVtBptFeSIhM9xlu sRTIDF2li6tA46U5BUrM0SVuR8sN/giHFCZU++WDySP20eo8sXNIkyItC3JP36mJc6/Q Mgva1x16M1PUv80ZclYg4DDdSXKDl1J9aKl5vpK8dO85EwTZJ1oGzbGfPlW7xNYibIbQ +Pn2mipQp1eKs4hGLMR+KjRoQrAsWP01sdX98PwvHBpeWl/vDQuxKMBKMzx44K7+zI3c Uz3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1DliN9cWI9tOr6qCWIwnsIRGllVyzqzKKx/V7aOAhqw=; b=LsyH+SxfPWMmJfHZYj4sjRfYwgvzawu7amZYiEjE4vcMDerTXxoPzsd9jCU67mR1Qh vgV/EOohxWOU2bvUgjoPZF2D3hR4PUGMsItXEb2NMPAVEBVakZ5eisChDk5Ze3M9+E3y xpu7YNRcZKbYrxgXU65Rr/hyZAmcdYdJIN+iCtN5n/h7F4erkAtI+CO2rRK9VMzc6WNq 3uP3cP0l2oAp4AQ/h0oXtaku8CFZLJoZtbfxb8Gc23oy8Nn3z1QYB7L8QaPqklKlumRI sB1HpbBgh9Xmh3jiN+IjF5dAtkn+1+X4vDhrw2AWlng0wxf9Lovc/feEK/OD56ESjTcZ oFQA== X-Gm-Message-State: AOAM530wLQV/wZpZANuL7cVT67HDjQvLo+3XATC9ec5ChFyXUR8DG3HN cclfv80ec7P8XYw7StoA9VZrRQhDBJXfd5Qacfk= X-Received: by 2002:a05:6602:2055:: with SMTP id z21mr7237276iod.60.1591337626749; Thu, 04 Jun 2020 23:13:46 -0700 (PDT) MIME-Version: 1.0 References: <20200602045506.40574-1-navid.emamdoost@gmail.com> In-Reply-To: From: Navid Emamdoost Date: Fri, 5 Jun 2020 01:13:35 -0500 Message-ID: Subject: Re: [PATCH] spi: tegra114: missing put on pm_runtime_get_sync failure To: Jon Hunter Cc: Laxman Dewangan , Mark Brown , Thierry Reding , linux-spi@vger.kernel.org, linux-tegra@vger.kernel.org, LKML , Navid Emamdoost , Qiushi Wu , Kangjie Lu , mccamant@cs.umn.edu Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 5, 2020 at 1:09 AM Jon Hunter wrote: > > > On 02/06/2020 05:55, Navid Emamdoost wrote: > > the call to pm_runtime_get_sync increments the counter even > > in case of failure leading to incorrect ref count. > > Call pm_runtime_put if pm_runtime_get_sync fails. > > > > Signed-off-by: Navid Emamdoost > > --- > > drivers/spi/spi-tegra114.c | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git a/drivers/spi/spi-tegra114.c b/drivers/spi/spi-tegra114.c > > index 83edabdb41ad..dccd2ac1a975 100644 > > --- a/drivers/spi/spi-tegra114.c > > +++ b/drivers/spi/spi-tegra114.c > > @@ -974,6 +974,7 @@ static int tegra_spi_setup(struct spi_device *spi) > > dev_err(tspi->dev, "pm runtime failed, e = %d\n", ret); > > if (cdata) > > tegra_spi_cleanup(spi); > > + pm_runtime_put(tspi->dev); > > return ret; > > } > > > > @@ -1398,6 +1399,7 @@ static int tegra_spi_probe(struct platform_device *pdev) > > ret = pm_runtime_get_sync(&pdev->dev); > > if (ret < 0) { > > dev_err(&pdev->dev, "pm runtime get failed, e = %d\n", ret); > > + pm_runtime_put(&pdev->dev); > > goto exit_pm_disable; > > } > > I am wondering if it is better we use put_sync() here to ensure that > this happens before we exit the probe. To be honest I am not sure when to use different flavors of pm_runtime_put (like pm_runtime_put_noidle, pm_runtime_put_autosuspend, pm_runtime_put_sync, pm_runtime_put, pm_runtime_put_sync_suspend). I'd appreciate it if you could give me a pointer on how to decide on this. > > Jon > > -- > nvpublic -- Navid.