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  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, 8 Dec 2007 01:21:22 +0100
From:	Andi Kleen <>
To:	Pavel Machek <>
Cc:	"David P. Reed" <>,
	Andi Kleen <>,,
	Thomas Gleixner <>,
	Ingo Molnar <>,
	"H. Peter Anvin" <>
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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists