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: Thu, 24 Aug 2017 06:38:09 -0700 From: Christoph Hellwig <hch@...radead.org> To: Jan Kara <jack@...e.cz> Cc: Christoph Hellwig <hch@...radead.org>, linux-fsdevel@...r.kernel.org, linux-nvdimm@...ts.01.org, Andy Lutomirski <luto@...nel.org>, linux-ext4@...r.kernel.org, linux-xfs@...r.kernel.org, Ross Zwisler <ross.zwisler@...ux.intel.com>, Dan Williams <dan.j.williams@...el.com>, Boaz Harrosh <boazh@...app.com> Subject: Re: [PATCH 11/13] dax, iomap: Add support for synchronous faults On Thu, Aug 24, 2017 at 02:34:51PM +0200, Jan Kara wrote: > In a subtle but important way ;). The main difference is that if the extent > has been already allocated by previous write, but the changing transaction > is not yet committed, we will return IOMAP_F_NEEDDSYNC but not IOMAP_F_NEW. Ok. How about a IOMAP_F_DIRTY flag and a better explanation?
Powered by blists - more mailing lists