From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: Shyam-sundar.S-k@amd.com, Hans de Goede <hansg@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
mario.limonciello@amd.com, platform-driver-x86@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] platform/x86/amd/pmc: Fix RTC device leak in amd_pmc_verify_czn_rtc()
Date: Thu, 17 Sep 2026 17:06:10 +0300 (EEST) [thread overview]
Message-ID: <f320a056-78a6-c33b-9d75-8298f140283b@linux.intel.com> (raw)
In-Reply-To: <20260917135854.2154187-1-vulab@iscas.ac.cn>
On Thu, 17 Sep 2026, Wentao Liang wrote:
> rtc_class_open() takes a reference to the RTC device, but all paths
> that return after it succeeded, apart from the final one where the
> alarm is programmed, leave the function without dropping it. Route
> them through a common exit that calls rtc_class_close().
>
> Fixes: 59348401ebed ("platform/x86: amd-pmc: Add special handling for timer based S0i3 wakeup")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
> drivers/platform/x86/amd/pmc/pmc.c | 21 ++++++++++++++-------
> 1 file changed, 14 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/platform/x86/amd/pmc/pmc.c b/drivers/platform/x86/amd/pmc/pmc.c
> index cae3fcafd4d7..f40e8d9b124a 100644
> --- a/drivers/platform/x86/amd/pmc/pmc.c
> +++ b/drivers/platform/x86/amd/pmc/pmc.c
> @@ -569,32 +569,39 @@ static int amd_pmc_verify_czn_rtc(struct amd_pmc_dev *pdev, u32 *arg)
> return 0;
> rc = rtc_read_alarm(rtc_device, &alarm);
> if (rc)
> - return rc;
> + goto out;
> if (!alarm.enabled) {
> dev_dbg(pdev->dev, "alarm not enabled\n");
> - return 0;
> + rc = 0;
> + goto out;
> }
> rc = rtc_read_time(rtc_device, &tm);
> if (rc)
> - return rc;
> + goto out;
> then = rtc_tm_to_time64(&alarm.time);
> now = rtc_tm_to_time64(&tm);
> duration = then-now;
>
> /* in the past */
> - if (then < now)
> - return 0;
> + if (then < now) {
> + rc = 0;
> + goto out;
> + }
>
> /* will be stored in upper 16 bits of s0i3 hint argument,
> * so timer wakeup from s0i3 is limited to ~18 hours or less
> */
> - if (duration <= 4 || duration > U16_MAX)
> - return -EINVAL;
> + if (duration <= 4 || duration > U16_MAX) {
> + rc = -EINVAL;
> + goto out;
> + }
>
> *arg |= (duration << 16);
> rc = rtc_alarm_irq_enable(rtc_device, 0);
> pm_pr_dbg("wakeup timer programmed for %lld seconds\n", duration);
>
> +out:
> + rtc_class_close(rtc_device);
> return rc;
> }
I was expecting 2 patch series, with one which adds the DEFINE_FREE() into
the public rtc header, not going back to the old approach. You also seemed
to forget to increase the version number in the subject.
--
i.
next prev parent reply other threads:[~2026-09-17 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 13:58 [PATCH] platform/x86/amd/pmc: Fix RTC device leak in amd_pmc_verify_czn_rtc() Wentao Liang
2026-09-17 14:06 ` Ilpo Järvinen [this message]
2026-09-17 14:09 ` Ilpo Järvinen
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=f320a056-78a6-c33b-9d75-8298f140283b@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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.