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: Mon, 31 Dec 2007 13:21:00 +0000 From: Pavel Machek <pavel@....cz> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Rene Herman <rene.herman@...access.nl>, Ingo Molnar <mingo@...e.hu>, Alan Cox <alan@...rguk.ukuu.org.uk>, dpreed@...d.com, Islam Amer <pharon@...il.com>, hpa@...or.com, Ingo Molnar <mingo@...hat.com>, Andi Kleen <andi@...stfloor.org>, Thomas Gleixner <tglx@...utronix.de>, Linux Kernel <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] x86: provide a DMI based port 0x80 I/O delay override Hi! > > rene@...e4:~/src/port80$ su -c ./port80 > > cycles: out 2400, in 2401 > > rene@...e4:~/src/port80$ su -c ./port3cc > > cycles: out 459, in 394 > > > > As stated a few dozen times by now already, port 0x80 is _decidedly_ _non_ > > _random_ > > Oh, I agree 100% that port 80 is not random. It's very much selected on > purpose. > > The reason we use port 80 is because it's commonly used as the BIOS POST > debug port, which means that it's been a reasonable "safe" port to use, > since nobody would be so crazy as to actually hook up a real device behind > that port (and since it is below 0x100, it's also part of the "motherboard > range", so you won't have any crazy plug-in devices either). Eh? I have two mainboards here that have debug displays hooked to port 0x80. I have PCI DEBUG card that has display on port 0x80. "You plug in PCI DEBUG card and it overclocks your machine" is bad scenario.. (I don't know if it does... can PCI card emulate ISA timings?) 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