| 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
| ||
|
Date: Fri, 2 Mar 2007 14:58:10 +0100 From: Pavel Machek <pavel@....cz> To: Matthew Garrett <mjg59@...f.ucam.org> Cc: Jean Delvare <khali@...ux-fr.org>, Chuck Ebbert <cebbert@...hat.com>, Rudolf Marek <r.marek@...embler.cz>, linux-acpi@...r.kernel.org, linux-kernel <linux-kernel@...r.kernel.org>, lm-sensors@...sensors.org Subject: Re: [lm-sensors] Could the k8temp driver be interfering with ACPI? On Fri 2007-03-02 11:47:47, Matthew Garrett wrote: > On Fri, Mar 02, 2007 at 12:40:23PM +0100, Pavel Machek wrote: > > > Whitelist seems like a way to go :(. > > The DSDT code clearly can't touch the hardware itself - hardware access > is carried out by the kernel. If we can identify cases where ACPI reads > and writes would touch resources claimed by other drivers, that would be > a good starting point for working out what's going on. > > Of course, this ignores the case where the DSDT just traps into SMM > code. That one is clearly unsolvable. We can't solve SMM stuff. (Whitelist needed :-). Actually for the acpi stuff... we might wrap ACPI interpretter with a semaphore that needs to be taken before starting any AML code. Then just make sure sensors take same semaphore? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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/
Powered by blists - more mailing lists