linux-kernel - Re: lib/iomap.c mmio_{in,out}s* vs. __raw

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1162788631.28571.290.camel@localhost.localdomain>
Date:	Mon, 06 Nov 2006 15:50:31 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Linus Torvalds <torvalds@...l.org>
Cc:	Russell King <rmk+lkml@....linux.org.uk>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Jeff Garzik <jgarzik@...ox.com>, Andrew Morton <akpm@...l.org>,
	"David S. Miller" <davem@...emloft.net>,
	Paul Mackerras <paulus@...ba.org>
Subject: Re: lib/iomap.c mmio_{in,out}s* vs. __raw_* accessors

On Sun, 2006-11-05 at 19:13 -0800, Linus Torvalds wrote:
> 
> On Mon, 6 Nov 2006, Benjamin Herrenschmidt wrote:
> > 
> > In fact, you might want to push it to 2.6.19 since it fixes a bug
> > (current _be operations are incorrect for PIO without the patch).
> 
> Well, I doubt anybody uses them (or we'd have seen the problem), and more 
> importantly, I've already blown the patch away. If you think it's easier 
> for you to sync up later, though, I'll happily apply it. Mind sending it 
> back to me with a Tested-by: line or something? I literally didn't even 
> compile-test the thing, and blew that file away after I had generated the 
> trial patch.

I'll send it to you later then, in the merge window, along with the
stuff that uses it. That will give me a bit more time to actually test
it.

Cheers,
Ben.


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