linux-kernel - Re: ACPI OSI disaster on latest HP laptops

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

Message-Id: <200808031923.09414.trenn@suse.de>
Date:	Sun, 3 Aug 2008 19:23:08 +0200
From:	Thomas Renninger <trenn@...e.de>
To:	Len Brown <lenb@...nel.org>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	"linux-acpi" <linux-acpi@...r.kernel.org>,
	"Moore, Robert" <robert.moore@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andi Kleen <ak@...ux.intel.com>,
	Christian Kornacker <ckornacker@...e.de>
Subject: Re: ACPI OSI disaster on latest HP laptops - critical temperature shutdown

On Friday 01 August 2008 11:08:08 pm Len Brown wrote:
> [yet another resend]
>
> On Sat, 26 Jul 2008, Len Brown wrote:
> > On Fri, 25 Jul 2008, Rafael J. Wysocki wrote:
> > > On Friday, 25 of July 2008, Thomas Renninger wrote:
> > > > On Friday 25 July 2008 02:04:32 Len Brown wrote:
> > >
> > > [--snip--]
> > >
> > > > Len, this is not about the thermal zone, it is just
> > > > a real-world example of something I told you will happen
> > > > if Linux stays _OSI transparent with Windows.
> > > >
> > > > This is about that they have to provide a BIOS hot-fix for
> > > > VISTA or VISTA SP and thus breaking Linux because there
> > > > is no way to distinguish anymore.
> > > > Windows 2007 likely will have that fixed and they provide
> > > > a sane _CRT trip point again.
If Windows is returning true for all ever existing OSI(Windows XY) versions as 
Linux is doing it and they stick to that in the future, then my above 
assumption is not true.

Thanks to Matthew Garret pointing to the relevant Microsoft documentation.

> > > > This is an example of Windows versions workarounds that could
> > > > get much more complex, like initializing HW differently or
> > > > whatever.
> > > > _OSI is used by vendors as a convenient possibility to
> > > > adjust/workaround Windows bugs in their BIOSes, without
> > > > the need to pay Millions to Microsoft to fix their things.

If the next Windows version also returns true for the one for which the 
workaround applies to, they have to take care that only the one OS is 
matching in a follow up update, e.g.:
And(brokenOS, !new_OSes)
So this should make half way sure that vendors do not mis-use this too often.
Also it is ensured that the next Linux kernel generation returning 
OSI(newOSes) will get the correct AML code again.

And distributions can still offer OSI(supported dist) for emergencies.

Sorry for the loud noise.
I am convinced now that it is not that bad as it first looked like.

Thanks for all the input/feedback,

          Thomas
--
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/