----- Original Message ----- | Instead of zeroing out fallocated blocks in gfs2_iomap_alloc, zero them | out in fallocate_chunk, much higher up the call stack. This gets rid of | gfs2's abuse of the IOMAP_ZERO flag as well as the gfs2 specific zeronew | buffer flag. I can't think of a reason why zeroing out the blocks in | gfs2_iomap_alloc would have any benefits: there is no additional locking | at that level that would add protection to the newly allocated blocks. | | While at it, change fallocate over from gs2_block_map to gfs2_iomap_begin. | | Signed-off-by: Andreas Gruenbacher <agruenba@xxxxxxxxxx> | --- Hi, Thanks. This is now pushed to the for-next branch of the linux-gfs2 tree: https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=fffb64127adc3eea6a19ceefdc88d171f68b9d34 Regards, Bob Peterson Red Hat File Systems
