netdev - Re: [PATCH] r8169: use correct barrier between cacheable and non-cacheable memory

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

Message-Id: <20100304.004048.09651248.davem@davemloft.net>
Date:	Thu, 04 Mar 2010 00:40:48 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	dave@...dillows.org
Cc:	netdev@...r.kernel.org, romieu@...zoreil.com, paulus@...ba.org,
	catalin.marinas@....com
Subject: Re: [PATCH] r8169: use correct barrier between cacheable and
 non-cacheable memory

From: David Dillow <dave@...dillows.org>
Date: Wed, 03 Mar 2010 21:33:10 -0500

> r8169 needs certain writes to be visible to other CPUs or the NIC before
> touching the hardware, but was using smp_wmb() which is only required to
> order cacheable memory access. Switch to wmb() which is required to
> order both cacheable and non-cacheable memory.
> 
> Noticed by Catalin Marinas and Paul Mackerras.
> 
> Signed-off-by: David Dillow <dave@...dillows.org>

Applied.
--
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