netdev - Re: [PATCH net] net/mlx4_en: correct the endianness of doorbell

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20141213.234320.1607496855879763694.davem@davemloft.net>
Date:	Sat, 13 Dec 2014 23:43:20 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	weiyang@...ux.vnet.ibm.com
Cc:	David.Laight@...LAB.COM, eric.dumazet@...il.com,
	netdev@...r.kernel.org, gideonn@...lanox.com, edumazet@...gle.com,
	amirv@...lanox.com
Subject: Re: [PATCH net] net/mlx4_en: correct the endianness of
 doorbell_qpn on big endian platform

From: Wei Yang <weiyang@...ux.vnet.ibm.com>
Date: Sat, 13 Dec 2014 11:13:38 +0800

> On Mon, Dec 08, 2014 at 10:42:37PM +0800, Wei Yang wrote:
> If you prefer this way, I would like to send a new version for this.
> Is it ok for you?

I'm not so sure.  There are implications when using the __raw_*()
routines.

In particular, using __raw_{read,write}l() also means that the usual
necessary I/O memory barriers are not being performed.

There are therefore no ordering guarantees between __raw_*() and other
I/O or memory accesses whatsoever.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html