linux-kernel - Re: [RT] [RFC] simple SMI detector

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]

Date:	Sat, 24 Jan 2009 17:30:30 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Lee Revell <rlrevell@...-job.com>
cc:	Jon Masters <jcm@...hat.com>, linux-rt-users@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	williams <williams@...hat.com>,
	"Luis Claudio R. Goncalves" <lgoncalv@...hat.com>
Subject: Re: [RT] [RFC] simple SMI detector

On Fri, 23 Jan 2009, Lee Revell wrote:
> 
> FYI the RTAI project has a patch to allow disabling of SMI:
> 
> https://listas.upv.es/pipermail/rtlinuxgpl/2007-April/000609.html

FYI, this patch should be removed from the internet archives and the
author should be made liable for the damage which can happen when
innocent users try to use it for fixing things which simply can not be
fixed.

>> .... disabled SMIs with RTAI code the latencies of cyclictest were
>> good, but after about 20 minutes my system stopped working and now
>> it does not even boot anymore. :( Any hint?
>
> Yeah. Buy a new CPU. You deep-fried your P4 because you disabled the
> thermal protection.

Aside of this worst case scenario, disabling SMIs is problematic as
SMI is used to emulate devices, to fix chip bugs and necessary for
enhanced features.

The only reasonable thing you can do on a SMI plagued system is to
identify the device which makes use of SMIs. Legacy ISA devices and
USB are usually good candidates. If that does not help, don't use it
for real-time :)

Thanks,

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