From: Johan Hovold <johan@kernel.org>
To: Guangshuo Li <lgs201920130244@gmail.com>
Cc: Min Ma <mamin506@gmail.com>, Lizhi Hou <lizhi.hou@amd.com>,
Oded Gabbay <ogabbay@kernel.org>,
Karol Wachowski <karol.wachowski@linux.intel.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] accel/amdxdna: fix usage_count leak when autosuspend_delay is negative
Date: Tue, 18 Aug 2026 11:20:37 +0200 [thread overview]
Message-ID: <aoQj5S4CQIVicL_T@hovoldconsulting.com> (raw)
In-Reply-To: <20260807143200.2500342-1-lgs201920130244@gmail.com>
On Fri, Aug 07, 2026 at 10:32:00PM +0800, Guangshuo Li wrote:
> amdxdna_pm_init() calls pm_runtime_use_autosuspend(), but
> amdxdna_pm_fini() does not call the matching
> pm_runtime_dont_use_autosuspend() when tearing down runtime PM.
>
> If 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
> driver teardown, this reference is not dropped and usage_count remains
> unbalanced.
As I've explained elsewhere, this is just misleading. There is no usage
count leak here as the count is balanced whenever the user re-enables
autosuspend through sysfs (by writing a non-negative timeout).
Drivers should clean up after themselves and disable autosuspend, but
this is more of a clean up than a fix and should not be backported.
You've sent upwards of 60 of these in the matter of just a few days,
some of which have even been picked up. Please send follow-ups (replies
or v2s) as soon as possible to prevent further of these from getting
merged.
> Add the missing pm_runtime_dont_use_autosuspend() call in
> amdxdna_pm_fini() before restoring the runtime PM usage reference and
> forbidding runtime PM.
>
> This issue was found by manual code inspection.
>
> Fixes: 063db451832b ("accel/amdxdna: Enhance runtime power management")
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
Johan
prev parent reply other threads:[~2026-08-18 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 14:32 Guangshuo Li
2026-08-18 9:20 ` Johan Hovold [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=aoQj5S4CQIVicL_T@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=karol.wachowski@linux.intel.com \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=mamin506@gmail.com \
--cc=ogabbay@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
all inboxes | Powered by JetHome®