linux-kernel - [PATCH 0/3] PCI / ACPI / PM: Fix propagation of wakeup settings to bridges

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 for Android: free password hash cracker in your pocket

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

Message-ID: <3116391.JNS1F4DjTg@aspire.rjw.lan>
Date:   Fri, 21 Jul 2017 14:36:44 +0200
From:   "Rafael J. Wysocki" <rjw@...ysocki.net>
To:     Linux PCI <linux-pci@...r.kernel.org>
Cc:     Linux ACPI <linux-acpi@...r.kernel.org>,
        Linux PM <linux-pm@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>,
        Bjorn Helgaas <bhelgaas@...gle.com>
Subject: [PATCH 0/3] PCI / ACPI / PM: Fix propagation of wakeup settings to bridges

Hi,

The device wakeup code in pci-acpi.c currently has a (theoretical) problem that
it can disable wakeup for a bridge prematurely in some obscure conditions.

This is described in some more detail in the changelog of patch [3/3] and it
has been there for quite a while, so it's nothing new, but it would be good
to fix it at last and hence this series.

Patches [1/3] and [2/3] are mostly preparatory, although the former may be
regarded as a fix by itself and the latter is a cleanup.

Thanks,
Rafael