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
| ||
|
Message-ID: <20071208002122.GC5992@one.firstfloor.org> Date: Sat, 8 Dec 2007 01:21:22 +0100 From: Andi Kleen <andi@...stfloor.org> To: Pavel Machek <pavel@....cz> Cc: "David P. Reed" <dpreed@...d.com>, Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com> Subject: Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops On Wed, Dec 05, 2007 at 11:10:39AM +0000, Pavel Machek wrote: > On Fri 2007-12-07 09:50:26, David P. Reed wrote: > > My machine in question, for example, needs no waiting > > within CMOS_READs at all. And I doubt any other > > chip/device needs waiting that isn't already provided by > > the bus. the i/o to port 80 is very, very odd in this > > context. Actually, modern machines have potentially > > more serious problems with i/o ops to non-existent > > addresses, which may cause real bus wierdness. > > I dislike outb_p clobbering port 0x80, but you are wrong here. BIOSes > already do outs to port 0x80 for debugging reason, so these accesses > are unlikely to do something bad. They only do that briefly during boot though. But Linux can do it much more often. If it's a race or similar it might just not trigger with the BIOS. -Andi -- 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