| 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
| ||
|
Message-Id: <20100614093444O.fujita.tomonori@lab.ntt.co.jp> Date: Mon, 14 Jun 2010 09:35:59 +0900 From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> To: catalin.marinas@....com Cc: npiggin@...e.de, hancockrwd@...il.com, tj@...nel.org, linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org, colin.tuckley@....com, jeff@...zik.org, linux-arch@...r.kernel.org Subject: Re: [PATCH v2] sata_sil24: Use memory barriers before issuing commands On Fri, 11 Jun 2010 10:41:46 +0100 Catalin Marinas <catalin.marinas@....com> wrote: > On Fri, 2010-06-11 at 02:38 +0100, Nick Piggin wrote: > > On Thu, Jun 10, 2010 at 06:43:03PM -0600, Robert Hancock wrote: > > > IMHO, it would be better for the platform code to ensure that MMIO > > > access was strongly ordered with respect to each other and to RAM > > > access. Drivers are just too likely to get this wrong, especially > > > when x86, the most tested platform, doesn't have such issues. > > > > The plan is to make all platforms do this. writes should be > > strongly ordered with memory. That serves to keep them inside > > critical sections as well. > > Are there any public references to this discussion? Maybe a > Documentation/ file (or update the memory-barriers.txt one would be > useful). I guess, http://marc.info/?t=121185223900001&r=1&w=2 -- 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/
Powered by blists - more mailing lists