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
| ||
|
Message-ID: <20171013192653.GA29081@linux.intel.com> Date: Fri, 13 Oct 2017 13:26:53 -0600 From: Ross Zwisler <ross.zwisler@...ux.intel.com> To: Jan Kara <jack@...e.cz> Cc: linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, linux-xfs@...r.kernel.org, Christoph Hellwig <hch@...radead.org>, Dan Williams <dan.j.williams@...el.com>, Ross Zwisler <ross.zwisler@...ux.intel.com>, Ted Tso <tytso@....edu>, "Darrick J. Wong" <darrick.wong@...cle.com> Subject: Re: [PATCH 11/19] dax: Allow tuning whether dax_insert_mapping_entry() dirties entry On Wed, Oct 11, 2017 at 10:05:55PM +0200, Jan Kara wrote: > Currently we dirty radix tree entry whenever dax_insert_mapping_entry() > gets called for a write fault. With synchronous page faults we would > like to insert clean radix tree entry and dirty it only once we call > fdatasync() and update page tables to same some unnecessary cache > flushing. Add 'dirty' argument to dax_insert_mapping_entry() for that. > > Signed-off-by: Jan Kara <jack@...e.cz> Looks good. Reviewed-by: Ross Zwisler <ross.zwisler@...ux.intel.com>
Powered by blists - more mailing lists