All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jesse Casco" <jesse.casco@gmail.com>
Cc: linux-rtc@vger.kernel.org,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH] rtc: interface: fix wakeup source leak in rtc_timer_do_work()
Date: Thu, 12 Nov 2026 00:45:58 +0000	[thread overview]
Message-ID: <sashiko-outbox-209985@kernel.org> (raw)
In-Reply-To: <20261112002125.24566-1-jesse.casco@gmail.com>

> rtc_update_irq(), rtc_set_time() and the -ETIME paths of
> rtc_timer_enqueue() and rtc_timer_remove() call pm_stay_awake() on the
> RTC parent device before scheduling rtc->irqwork, and
> rtc_timer_do_work() balances that with pm_relax() when it is done.
> 
> Since commit e8ba8a2bc4f6 ("rtc: check if __rtc_read_time was successful
> in rtc_timer_do_work()"), a failed time read returns early without
> calling pm_relax(). A single read error then leaves the wakeup source
> active, reads of /sys/power/wakeup_count block and suspend cannot
> proceed.
> 
> Seen on an ASUS Zenbook A16 (UX3607OA), where reads of the PMIC GLINK
> RTC time out and the pmic_glink.rtc-glink.0 wakeup source stays active
> from boot. With this change the source is released after each failed
> read.
> 
> Fixes: e8ba8a2bc4f6 ("rtc: check if __rtc_read_time was successful in rtc_timer_do_work()")
> Cc: stable@vger.kernel.org
> Signed-off-by: Jesse Casco <jesse.casco@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261112002125.24566-1-jesse.casco@gmail.com?part=1


      reply	other threads:[~2026-11-12  0:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12  0:21 [PATCH] rtc: interface: fix wakeup source leak in rtc_timer_do_work() Jesse Casco
2026-11-12  0:45 ` sashiko-bot [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=sashiko-outbox-209985@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=jesse.casco@gmail.com \
    --cc=linux-rtc@vger.kernel.org \
    --cc=sashiko-reviews@lists.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.