| Date | Wed, 16 Oct 2019 08:21:11 +1100 | From | Dave Chinner <> | Subject | Re: [PATCH 02/12] xfs: set IOMAP_F_NEW more carefully |
| |
On Tue, Oct 15, 2019 at 05:43:35PM +0200, Christoph Hellwig wrote: > Don't set IOMAP_F_NEW if we COW over and existing allocated range, as > these aren't strictly new allocations. This is required to be able to > use IOMAP_F_NEW to zero newly allocated blocks, which is required for > the iomap code to fully support file systems that don't do delayed > allocations or use unwritten extents. > > Signed-off-by: Christoph Hellwig <hch@lst.de>
looks fine.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
-- Dave Chinner david@fromorbit.com
|