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, 15 Aug 2015 11:05:26 -0700 From: Dan Williams <dan.j.williams@...el.com> To: Christoph Hellwig <hch@....de> Cc: Ross Zwisler <ross.zwisler@...ux.intel.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>, Jonathan Corbet <corbet@....net>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Paul Mackerras <paulus@...ba.org>, Michael Ellerman <mpe@...erman.id.au>, Jens Axboe <axboe@...nel.dk>, Martin Schwidefsky <schwidefsky@...ibm.com>, Heiko Carstens <heiko.carstens@...ibm.com>, linux390@...ibm.com, Alexander Viro <viro@...iv.linux.org.uk>, Matthew Wilcox <willy@...ux.intel.com>, Jeff Layton <jlayton@...marydata.com>, Andrew Morton <akpm@...ux-foundation.org>, Omar Sandoval <osandov@...ndov.com>, Boaz Harrosh <boaz@...xistor.com>, Miklos Szeredi <mszeredi@...e.cz>, Jan Kara <jack@...e.cz>, Wolfram Sang <wsa@...-dreams.de>, Uwe Kleine-König <u.kleine-koenig@...gutronix.de>, Gerald Schaefer <gerald.schaefer@...ibm.com>, Ameen Ali <ameenali023@...il.com>, "Martin K. Petersen" <martin.petersen@...cle.com>, Sagi Grimberg <sagig@...lanox.com>, Mike Snitzer <snitzer@...hat.com>, Tejun Heo <tj@...nel.org>, Shaohua Li <shli@...com>, Ming Lei <ming.lei@...onical.com>, linux-doc@...r.kernel.org, linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>, linux-s390@...r.kernel.org, linux-fsdevel <linux-fsdevel@...r.kernel.org>, Dave Chinner <david@...morbit.com> Subject: Re: [PATCH v2 7/7] pmem, dax: have direct_access use __pmem annotation On Sat, Aug 15, 2015 at 9:00 AM, Christoph Hellwig <hch@....de> wrote: > On Sat, Aug 15, 2015 at 08:44:27AM -0700, Dan Williams wrote: >> That said, while we don't need special accessors we do need guarantees >> that anything that has written to a persistent memory address has done >> so in a way that wmb_pmem() is able to flush it. It's more of a "I've >> audited this code path for wmb_pmem() compatibility so use this api to >> write to pmem." > > I'm more worried about things where don't just do plain loads and stores > to a pmem region but DMA, which will end up as a nightmare of casts. > > But we can wait and see how that evolves in the end.. It's already not possible to do something like dma_map_single() on an ioremap()'d address, so there currently are't any __iomem/DMA collisions. As long as DMA setup is relative to a physical address resource I think we're ok. Making sure a DMA is both complete and persistent though is a different problem. -- 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