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: Wed, 12 Dec 2007 16:12:45 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: unlisted-recipients:; (no To-header on input) Cc: "Rene Herman" <rene.herman@...access.nl>, "Paul Rolland" <rol@...917.net>, "H. Peter Anvin" <hpa@...or.com>, "Krzysztof Halasa" <khc@...waw.pl>, "Pavel Machek" <pavel@....cz>, "Andi Kleen" <andi@...stfloor.org>, <linux-kernel@...r.kernel.org>, "Thomas Gleixner" <tglx@...utronix.de>, "Ingo Molnar" <mingo@...hat.com>, <rol@...be.net> Subject: Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops There is another reason we can't just do a dumb changeover - two actually #1: Some drivers are using inb_p/outb_p in PCI cases which are going to cause PCI posting changes. Most are probably just wrong in the first place but they need hand checking #2: We've got SMP cases that only 'work' because the odds of splitting the outb and the following port 0x80 cycle, which locks the bus, are tiny. That is we've got CPU1 CPU2 main path irq path outb outb inb 0x80 inb 0x80 races in one or two spots. -- 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