From: Sergey Shtylyov <s.shtylyov@auroraos.dev>
To: Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulfh@kernel.org>, <linux-mmc@vger.kernel.org>
Cc: Jisheng Zhang <jszhang@kernel.org>
Subject: Re: [PATCH] mmc: sdhci-of-dwcmshc: check bus clock enable result in the, probe() method
Date: Fri, 29 May 2026 20:27:48 +0300 [thread overview]
Message-ID: <784193db-813b-4ef4-ab56-cbdfd73fe72a@auroraos.dev> (raw)
In-Reply-To: <34ef000c-907f-40b2-86e2-0c4fab094cfd@auroraos.dev>
On 5/28/26 11:42 PM, Sergey Shtylyov wrote:
> In the driver's probe() method, clk_disable_unprepare() for the bus clock
> is called on the error path even if the prior clk_prepare_enable() call has
> failed -- that causes the prepare/enable counter imbalance. Also, the same
I missed the fact that the remove() would be affected by the imbalance as well.
I'll update the description and repost...
> kind of problem can happen in the driver's suspend() method; note that the
> resume() method does check for the clk_prepare_enable()'s success -- let's
> just be consistent and do that in probe() method too (BTW, I don't know for
> sure what does the bus clock control -- if it affects the register access,
> the driver is likely to cause a kernel oops iff it fails to prepare/enable
> the bus clock in the probe() method)...
>
> Found by Linux Verification Center (linuxtesting.org) with the Svace static
> analysis tool.
>
> Fixes: e438cf49b305 ("mmc: sdhci-of-dwcmshc: add SDHCI OF Synopsys DWC MSHC driver")
> Fixes: bccce2ec7790 ("mmc: sdhci-of-dwcmshc: add suspend/resume support")
> Signed-off-by: Sergey Shtylyov <s.shtylyov@auroraos.dev>
[...]
MBR, Sergey
prev parent reply other threads:[~2026-05-29 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 20:42 [PATCH] mmc: sdhci-of-dwcmshc: check bus clock enable result in the, probe() method Sergey Shtylyov
2026-05-29 17:27 ` Sergey Shtylyov [this message]
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=784193db-813b-4ef4-ab56-cbdfd73fe72a@auroraos.dev \
--to=s.shtylyov@auroraos.dev \
--cc=adrian.hunter@intel.com \
--cc=jszhang@kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulfh@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