On Sat, Sep 13, 2014 at 03:13:06PM -0700, Darrick J. Wong wrote:
> In order to support fallocate, we need to be able to have
> ext2fs_bmap2() allocate blocks and put them into uninitialized
> extents. There's a flag to do this in the extent code, but it's not
> exposed to the bmap2 interface, so plumb that in. Eventually
> fallocate or fuse2fs or somebody will use it.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx>
> ---
> lib/ext2fs/bmap.c | 24 ++++++++++++++++++++++--
> lib/ext2fs/ext2fs.h | 1 +
> 2 files changed, 23 insertions(+), 2 deletions(-)
>
>
> diff --git a/lib/ext2fs/bmap.c b/lib/ext2fs/bmap.c
> index c1d0e6f..a4dc8ef 100644
> --- a/lib/ext2fs/bmap.c
> +++ b/lib/ext2fs/bmap.c
> @@ -72,6 +72,11 @@ static _BMAP_INLINE_ errcode_t block_ind_bmap(ext2_filsys fs, int flags,
> block_buf + fs->blocksize, &b);
> if (retval)
> return retval;
> + if (flags & BMAP_UNINIT) {
> + retval = ext2fs_zero_blocks2(fs, b, 1, NULL, NULL);
> + if (retval)
> + return retval;
> + }
What I think we should do is to have two separate new BMAP_ flags;
BMAP_UNINIT, which sets the uninit bit, and BMAP_ZERO, which requests
that the block be zeroed. I don't think it should follow that whe you
set the uninit bit via the libext2fs, the block wil automatically be
zeroed. After all, userspace can't assume that if the uninit bit is
set, that the block will be pre-zeroed, since files fallocated by the
kernel won't meet that guarantee.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
