On Tue 27-09-16 10:01:18, Christoph Hellwig wrote: > On Tue, Sep 27, 2016 at 06:43:33PM +0200, Jan Kara wrote: > > So far we did not set BH_New for newly allocated blocks for DAX inodes > > in __xfs_get_blocks() because we wanted to avoid zeroing done in generic > > DAX code which was racy. Now the zeroing is gone so we can remove this > > workaround and return BH_New for newly allocated blocks. DAX will use this > > information to properly update mappings of the file. > > __xfs_get_blocks isn't used by the DAX code any more. > xfs_file_iomap_begin should already be doing the right thing for now. OK, the changelog is stale but I actually took care to integrate this with your iomap patches and for the new invalidation code in iomap_dax_actor() to work we need this additional information... Honza -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
