Re: [PATCH] Btrfs: fix missing data checksums after a ranged fsync (msync)

2018-11-01 Thread David Sterba
On Mon, Oct 29, 2018 at 09:42:06AM +, fdman...@kernel.org wrote: > From: Filipe Manana > > Recently we got a massive simplification for fsync, where for the fast > path we no longer log new extents while their respective ordered extents > are still running. > > However that simplification

Re: [PATCH] Btrfs: fix missing data checksums after a ranged fsync (msync)

2018-10-31 Thread Josef Bacik
On Mon, Oct 29, 2018 at 09:42:06AM +, fdman...@kernel.org wrote: > From: Filipe Manana > > Recently we got a massive simplification for fsync, where for the fast > path we no longer log new extents while their respective ordered extents > are still running. > > However that simplification

[PATCH] Btrfs: fix missing data checksums after a ranged fsync (msync)

2018-10-29 Thread fdmanana
From: Filipe Manana Recently we got a massive simplification for fsync, where for the fast path we no longer log new extents while their respective ordered extents are still running. However that simplification introduced a subtle regression for the case where we use a ranged fsync (msync).