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: Mon, 13 Jul 2020 18:09:57 +0200 From: David Sterba <dsterba@...e.cz> To: Goldwyn Rodrigues <rgoldwyn@...e.de> Cc: Christoph Hellwig <hch@....de>, Dave Chinner <david@...morbit.com>, Damien Le Moal <damien.lemoal@....com>, Naohiro Aota <naohiro.aota@....com>, Johannes Thumshirn <jth@...nel.org>, Matthew Wilcox <willy@...radead.org>, linux-btrfs@...r.kernel.org, linux-fsdevel@...r.kernel.org, cluster-devel@...hat.com, linux-ext4@...r.kernel.org, linux-xfs@...r.kernel.org Subject: Re: [PATCH 2/2] iomap: fall back to buffered writes for invalidation failures On Mon, Jul 13, 2020 at 07:20:50AM -0500, Goldwyn Rodrigues wrote: > On 9:46 13/07, Christoph Hellwig wrote: > > Failing to invalid the page cache means data in incoherent, which is > > a very bad state for the system. Always fall back to buffered I/O > > through the page cache if we can't invalidate mappings. > > > > Signed-off-by: Christoph Hellwig <hch@....de> > > Thanks. This will help btrfs. The current next tree contains the iomap > changes I recomended and would need to be reverted in order to > incorporate this. Once this is in the next tree I will (re)format the > btrfs iomap dio patches. Patches in next don't need to be reverted, if you put together a branch with any iomap or other prep patches + btrfs iomap-dio I'll replace it in the for-next snapshot I push.
Powered by blists - more mailing lists