linux-kernel - [3.0.y, 3.2.y, 3.3.y] Re: [PATCH 04/76] ACPICA: Fix regression in FADT revision checks

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

Message-ID: <20120403195804.GA19239@burratino>
Date:	Tue, 3 Apr 2012 14:58:44 -0500
From:	Jonathan Nieder <jrnieder@...il.com>
To:	Greg Kroah-Hartman <greg@...ah.com>
Cc:	Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org,
	linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	Julian Anastasov <ja@....bg>, Len Brown <len.brown@...el.com>,
	Josh Boyer <jwboyer@...il.com>, wzab@....pw.edu.pl,
	stable@...r.kernel.org
Subject: [3.0.y, 3.2.y, 3.3.y] Re: [PATCH 04/76] ACPICA: Fix regression in
 FADT revision checks

Hi Greg,

Josh Boyer wrote:
> On Fri, Mar 30, 2012 at 6:13 AM, Len Brown <lenb@...nel.org> wrote:

>> From: Julian Anastasov <ja@....bg>
>>
>>        commit 64b3db22c04586997ab4be46dd5a5b99f8a2d390 (2.6.39),
>> "Remove use of unreliable FADT revision field" causes regression
>> for old P4 systems because now cst_control and other fields are
>> not reset to 0.
[...]
>>        The fix is to update acpi_gbl_FADT.header.length after
>> the original value is used to check for old revisions.
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=42700
>> https://bugzilla.redhat.com/show_bug.cgi?id=727865
>>
>> Signed-off-by: Julian Anastasov <ja@....bg>
>> Acked-by: Bob Moore <robert.moore@...el.com>
>> Signed-off-by: Len Brown <len.brown@...el.com>
>
> This one should go into the stable trees.

Please apply

  3e80acd1af40 "ACPICA: Fix regression in FADT revision checks"

which is in linus's master to the 3.0.y, 3.2.y, and 3.3.y series to
fix this old boot problem.  (Many affected people disabled HT in the
BIOS to work around it in the meantime.)

WZab (cc-ed) has tested that the patch addresses the problem when
applied to the 3.2.y and 3.3.y branches.  [1] has details.

Thanks,
Jonathan

[1] https://bugzilla.kernel.org/show_bug.cgi?id=38262
--
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/