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 14:34:51 +0200 From: Jan Kara <jack@...e.cz> To: Christoph Hellwig <hch@...radead.org> Cc: Jan Kara <jack@...e.cz>, 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 24-08-17 05:27:20, Christoph Hellwig wrote: > Just curious: how does IOMAP_F_NEEDDSYNC practically differ > from IOMAP_F_NEW? 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. Honza -- Jan Kara <jack@...e.com> SUSE Labs, CR
Powered by blists - more mailing lists