linux-kernel - Re: Do cpu-endian MMIO accessors exist?

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <200907220005.27583.arnd@arndb.de>
Date:	Wed, 22 Jul 2009 00:05:27 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	Pekka Paalanen <pq@....fi>, linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>
Subject: Re: Do cpu-endian MMIO accessors exist?

On Tuesday 21 July 2009, Jiri Slaby wrote:
> On 07/21/2009 11:15 PM, Arnd Bergmann wrote:
> > __raw_readl is not a replacement for real accessors like
> > ioread32 or in_be32, because it does not synchronize with the
> > instruction stream.
> 
> Aha, I see now. I guess it's a bug that ioread/write* on sh are not with
> barriers?

That depends on how that architecture defines its bus interface.
On many simple architectures, you do not need any synchronization
operations.

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