netdev - Re: [net-next 07/12] bna: CQ Read Fix

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: <20131214.015538.1434478935532675070.davem@davemloft.net>
Date:	Sat, 14 Dec 2013 01:55:38 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	rmody@...cade.com
Cc:	netdev@...r.kernel.org, adapter_linux_open_src_team@...cade.COM
Subject: Re: [net-next 07/12] bna: CQ Read Fix

From: Rasesh Mody <rmody@...cade.com>
Date: Thu, 12 Dec 2013 17:54:33 -0800

> Valid bit check for completion needs read fence, so that it does not get
> reordered with other loads.
> 
> Signed-off-by: Rasesh Mody <rmody@...cade.com>

All memory barriers added to code should have a big, verbose, comment
above it explaining exactly what the requirements are that will be
satisfied by the memory barrier.

Ie. what memory operation must be visible before or after what other
memory operation, and why?
--
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