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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 5 May 2020 12:43:19 +0200 From: Christoph Hellwig <hch@....de> To: Ritesh Harjani <riteshh@...ux.ibm.com> Cc: Christoph Hellwig <hch@....de>, linux-ext4@...r.kernel.org, viro@...iv.linux.org.uk, jack@...e.cz, tytso@....edu, adilger@...ger.ca, amir73il@...il.com, linux-fsdevel@...r.kernel.org, linux-unionfs@...r.kernel.org Subject: Re: [PATCH 09/11] fs: handle FIEMAP_FLAG_SYNC in fiemap_prep On Sat, May 02, 2020 at 04:22:31AM +0530, Ritesh Harjani wrote: > > > On 4/27/20 11:49 PM, Christoph Hellwig wrote: >> By moving FIEMAP_FLAG_SYNC handling to fiemap_prep we ensure it is >> handled once instead of duplicated, but can still be done under fs locks, >> like xfs/iomap intended with its duplicate handling. Also make sure the >> error value of filemap_write_and_wait is propagated to user space. > > > Forgot to remove filemap_write_and_wait() from > ext4_ioctl_get_es_cache() ? Fixed.
Powered by blists - more mailing lists