From: Baorui.Liu <baorliu@amd.com>
To: <rafael@kernel.org>
Cc: <linux-acpi@vger.kernel.org>, "Baorui . Liu" <baorliu@amd.com>
Subject: Re: [PATCH v3] ACPI: button: Report wakeup key only for power button wakeups
Date: Tue, 22 Sep 2026 10:23:30 +0800 [thread overview]
Message-ID: <20260922022330.490-1-baorliu@amd.com> (raw)
In-Reply-To: <CAJZ5v0jb7QNF32To0AoOBxXHObUAS7QCrFAGObFJU1=VtOqm+w@mail.gmail.com>
Hi Rafael,
I reviewed the Sashiko findings and agree with both of them.
1) High: race in acpi_button_suspend()
Clearing wakeup_pending after setting suspended=true can lose a
power-button SCI that arrives between the two stores. I will clear
wakeup_pending before setting suspended.
2) Medium: removing acpi_clear_event(POWER_BUTTON)
Dropping the status-bit clear can allow a deferred STATUS notify to
report KEY_POWER after resume has cleared suspended, which may confuse
userspace. I will keep clearing the fixed power-button status bit, mark
wakeup_pending so button resume can still report KEY_WAKEUP, and keep
the PM wakeup event on the fixed power-button device. KEY_WAKEUP is
still not synthesized from the generic ACPI sleep path for non-power
wakes.
I will send a v4 with these updates.
Thanks,
Baorui
next prev parent reply other threads:[~2026-09-22 2:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 12:27 [PATCH] ACPI: button: Report wakeup key only for power button wakeups Baorui Liu
2026-08-07 14:12 ` Rafael J. Wysocki (Intel)
2026-08-19 8:55 ` [PATCH v2 0/1] " Baorui.Liu
2026-08-19 8:55 ` [PATCH v2 1/1] " Baorui.Liu
2026-09-09 14:41 ` Rafael J. Wysocki (Intel)
2026-09-17 14:31 ` [PATCH v3] " Baorui.Liu
2026-09-18 14:36 ` Rafael J. Wysocki (Intel)
2026-09-22 2:23 ` Baorui.Liu [this message]
2026-09-22 2:42 ` [PATCH v4] " Baorui.Liu
2026-08-20 7:07 ` [PATCH] " kernel test robot
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=20260922022330.490-1-baorliu@amd.com \
--to=baorliu@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@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