| 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: Sun, 8 May 2016 02:01:15 -0700 From: "hch@...radead.org" <hch@...radead.org> To: "Verma, Vishal L" <vishal.l.verma@...el.com> Cc: "Williams, Dan J" <dan.j.williams@...el.com>, "hch@...radead.org" <hch@...radead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>, "xfs@....sgi.com" <xfs@....sgi.com>, "linux-nvdimm@...1.01.org" <linux-nvdimm@...1.01.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>, "viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>, "axboe@...com" <axboe@...com>, "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>, "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>, "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>, "david@...morbit.com" <david@...morbit.com>, "jack@...e.cz" <jack@...e.cz>, "matthew@....cx" <matthew@....cx> Subject: Re: [PATCH v4 5/7] fs: prioritize and separate direct_io from dax_io On Thu, May 05, 2016 at 09:45:07PM +0000, Verma, Vishal L wrote: > I'm not sure I completely understand how this will work? Can you explain > a bit? Would we have to export rw_bytes up to layers above the pmem > driver? Where does get_user_pages come in? A DAX filesystem can directly use the nvdimm layer the same way btt doe,s what's the problem? Re get_user_pages my idea was to simply use that to lock down the user pages so that we can call rw_bytes on it. How else would you do it? Do a kmalloc, copy_from_user and then another memcpy?
Powered by blists - more mailing lists