linux-kernel - [PATCH 0/2] ACPI: PM: s2idle: Harden the premature EC wakeups handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <9291082.ZuhHelrm8h@kreacher>
Date:   Wed, 25 Mar 2020 11:52:42 +0100
From:   "Rafael J. Wysocki" <rjw@...ysocki.net>
To:     Linux ACPI <linux-acpi@...r.kernel.org>
Cc:     Linux PM <linux-pm@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Zhang Rui <rui.zhang@...el.com>,
        Erik Kaneda <erik.kaneda@...el.com>,
        Bob Moore <robert.moore@...el.com>,
        Ondřej Caletka <ondrej@...etka.cz>
Subject: [PATCH 0/2] ACPI: PM: s2idle: Harden the premature EC wakeups handling

Hi All,

It turns out that the checks added by commit fdde0ff8590b ("ACPI: PM: s2idle:
Prevent spurious SCIs from waking up the system") were not precise enough and
there are cases in which it actually doesn't prevent the system from resuming
due to a spurious wakeup event coming from the EC.

To fix that issue, allow acpi_any_gpe_status_set() to skip one GPE from the
check carried out by it (patch [1/2]) and use that for skipping the EC GPE
from that check in the suspend-to-idle loop, which then allows the wakeup
events coming from the EC to be checked more precisely (patch [2/2]).

Thanks!