linux-kernel - Re: dsdt buggy acpi

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

Message-ID: <20080702144820.29f7d43d@linux360.ro>
Date:	Wed, 2 Jul 2008 14:48:20 +0300
From:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Justin Mattock <justinmattock@...il.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Subject: Re: dsdt buggy acpi

On Wed, 2 Jul 2008 11:09:35 +0100
Matthew Garrett <mjg59@...f.ucam.org> wrote:

> On Wed, Jul 02, 2008 at 08:25:55AM +0300, Eduard - Gabriel Munteanu
> wrote:
> 
> > Just one note here: DSDTs have nothing to do with the kernel. This
> > is just broken firmware. The most one can do _in-kernel_ is
> > blacklist some functionality or create a workaround, but this only
> > happens for widely used stuff. Broken DSDTs aren't widely used
> > stuff, they are written by the machine's vendor (the laptop's
> > manufacturer for example, but this could be different for desktops)
> > and differ a lot from one machine to another.
> 
> We've made a huge number of workarounds for buggy DSDT
> implementations.

Of course, I myself used a custom DSDT for my laptop. But I was saying
that these workarounds generally do not belong to the kernel realm.

This isn't the regular "Pentium F00F bug" stuff; instead bugs in DSDTs
consist of compiling issues, non-standard compliant, plainly bad
code, Windows-only stuff, which can all be unique for every model of a
laptop for example. While the kernel may be able to get around some of
that stuff, the kernel won't have any Asus, Acer etc. specific
workarounds.
--
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/