linux-kernel - [git pull] ACPI patches for 2.6.27-rc7

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>] [day] [month] [year] [list]

Message-id: <alpine.LFD.2.00.1012261740390.2945@x980>
Date:	Sun, 26 Dec 2010 17:41:49 -0500 (EST)
From:	Len Brown <lenb@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [git pull] ACPI patches for 2.6.27-rc7

Hi Linus,

please pull from: 

git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git release

Some regression fixes for your stocking:-)

This will update the files shown below.

thanks!

--
Len Brown
Intel Open Source Technology Center


ps. individual patches are available on linux-acpi@...r.kernel.org
and a consolidated plain patch is available here:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/2.6.37/acpi-release-20101013-2.6.37-rc7.diff.gz

 drivers/acpi/acpica/evgpeinit.c |    3 +
 drivers/acpi/battery.c          |    5 --
 drivers/acpi/scan.c             |   97 ++++++++++++++++++++++++---------------
 3 files changed, 63 insertions(+), 42 deletions(-)

through these commits:

Len Brown (1):
      Revert "ACPI battery: update status upon sysfs query"

Rafael J. Wysocki (2):
      ACPI: Execute _PRW for devices reported as inactive or not present
      ACPI / ACPICA: Disable GPEs during initialization

with this log:

commit bbbcde9d9614683fbeb41f00728cfbfb7f75a7ad
Merge: d7c1255 5acdb1a cde44d1
Author: Len Brown <len.brown@...el.com>
Date:   Sun Dec 26 17:05:07 2010 -0500

    Merge branches 'bugzilla-25412' and 'bugzilla-25302' into release

commit 5acdb1af907d5908b4942d425c0983f353dd8fc5
Author: Rafael J. Wysocki <rjw@...k.pl>
Date:   Sun Dec 26 12:47:06 2010 +0100

    ACPI / ACPICA: Disable GPEs during initialization
    
    GPEs with corresponding _Lxx/_Exx control methods need to be disabled
    during initialization in case they have been enabled by the BIOS, so
    that they don't fire up until they are enabled by acpi_update_gpes().
    
    References: https://bugzilla.kernel.org/show_bug.cgi?id=25412
    Signed-off-by: Rafael J. Wysocki <rjw@...k.pl>
    Signed-off-by: Len Brown <len.brown@...el.com>

commit cde44d1740bcb3dcfecbf792a71826431e61686e
Author: Len Brown <len.brown@...el.com>
Date:   Fri Dec 24 21:43:16 2010 -0500

    Revert "ACPI battery: update status upon sysfs query"
    
    This reverts commit 3138b32d5e0998ba3cbd1c74bdc1887d74c5279b.
    
    as it caused a crash upon battery removal:
    https://bugzilla.kernel.org/show_bug.cgi?id=25302
    
    Signed-off-by: Len Brown <len.brown@...el.com>

commit b581a7f9c3abc6c7afacd021747543d32ff17adb
Author: Rafael J. Wysocki <rjw@...k.pl>
Date:   Fri Dec 17 22:34:01 2010 +0100

    ACPI: Execute _PRW for devices reported as inactive or not present
    
    If a device is reported as inactive or not present by its _STA
    control method, acpi_bus_check_add() skips it without evaluating its
    _PRW method.  This leads to a problem when the device's _PRW method
    points to a GPE, because in that case the GPE may be enabled by
    ACPICA during the subsequent acpi_update_gpes() call which, in
    turn, may cause a GPE storm to appear.
    
    To avoid this issue, make acpi_bus_check_add() evaluate _PRW for
    inactive or not present devices and register the wakeup GPE
    information returned by them, so that acpi_update_gpes() does not
    enable their GPEs unnecessarily.
    
    Signed-off-by: Rafael J. Wysocki <rjw@...k.pl>
    Reported-by: Matthew Garrett <mjg@...hat.com>
    Signed-off-by: Len Brown <len.brown@...el.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/