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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <200807251726.14366.rjw@sisk.pl>
Date:	Fri, 25 Jul 2008 17:26:13 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Thomas Renninger <trenn@...e.de>
Cc:	Len Brown <lenb@...nel.org>,
	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, 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.
> 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.

This is a valid point, IMO.

If vendors use _OSI(Windows) to work around Windows bugs, we get broken
automatically on those systems unless we put in some DMI-based hacks.

Thanks,
Rafael
--
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/