From: Maxime MERE <maxime.mere@foss.st.com>
To: Guangshuo Li <lgs201920130244@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Thorsten Blum <thorsten.blum@linux.dev>,
"lionel.debieve@st.com" <lionel.debieve@st.com>,
<linux-crypto@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <stable@vger.kernel.org>
Subject: Re: [PATCH] crypto: stm32/hash: fix autosuspend cleanup during teardown
Date: Fri, 14 Aug 2026 13:44:25 +0200 [thread overview]
Message-ID: <fc5c6571-34e5-408c-a6f0-e5cd46c816d6@foss.st.com> (raw)
In-Reply-To: <20260808094114.2750088-1-lgs201920130244@gmail.com>
On 8/8/26 11:41, Guangshuo Li wrote:
> stm32_hash_probe() calls pm_runtime_use_autosuspend(), but neither the
> probe failure path nor stm32_hash_remove() calls the matching
> pm_runtime_dont_use_autosuspend() before disabling runtime PM.
>
> If the autosuspend delay is set to a negative value while autosuspend
> is enabled, the runtime PM core increments usage_count to prevent
> runtime suspend. Without calling pm_runtime_dont_use_autosuspend()
> during teardown, this reference is not dropped and usage_count remains
> unbalanced.
>
> Add the missing pm_runtime_dont_use_autosuspend() calls to both the
> probe failure and remove paths before disabling runtime PM.
>
> This issue was found by manual code inspection.
>
> Fixes: 8b4d566de6a5 ("crypto: stm32/hash - Add power management support")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
Reviewed-by: Maxime Méré <maxime.mere@foss.st.com>
Cheers,
Maxime
next prev parent reply other threads:[~2026-08-14 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 9:41 [PATCH] crypto: stm32/hash: fix autosuspend cleanup during teardown Guangshuo Li
2026-08-14 11:44 ` Maxime MERE [this message]
2026-08-20 14:03 ` Krzysztof Kozlowski
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=fc5c6571-34e5-408c-a6f0-e5cd46c816d6@foss.st.com \
--to=maxime.mere@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=lgs201920130244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lionel.debieve@st.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=stable@vger.kernel.org \
--cc=thorsten.blum@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.