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
| ||
|
Date: Sat, 9 Sep 2006 12:03:29 +1000 From: Paul Mackerras <paulus@...ba.org> To: torvalds@...l.org CC: linux-kernel@...r.kernel.org, benh@...nel.crashing.org, akpm@...l.org, segher@...nel.crashing.org, davem@...emloft.net Subject: Opinion on ordering of writel vs. stores to RAM Linus, An issue has come up in the tg3 ethernet driver, where we are seeing data corruption on ppc64 machines that is attributable to a lack of ordering between writes to normal RAM and writes to an MMIO register. Basically the driver does writes to RAM and then a writel to an MMIO register to trigger DMA, and occasionally the device then reads old values from memory. Do you have an opinion about whether the MMIO write in writel() should be ordered with respect to preceding writes to normal memory? Currently we have a sync instruction after the store in writel() but not one before. The sync after is to keep the writel inside spinlocked regions and to ensure that the store is ordered with respect to the load in readl() and friends. Paul. - 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