• Christoph Hellwig's avatar
    xfs: handle nimaps=0 from xfs_bmapi_write in xfs_alloc_file_space · 35dc55b9
    Christoph Hellwig authored
    If xfs_bmapi_write finds a delalloc extent at the requested range, it
    tries to convert the entire delalloc extent to a real allocation.
    
    But if the allocator cannot find a single free extent large enough to
    cover the start block of the requested range, xfs_bmapi_write will
    return 0 but leave *nimaps set to 0.
    
    In that case we simply need to keep looping with the same startoffset_fsb
    so that one of the following allocations will eventually reach the
    requested range.
    
    Note that this could affect any caller of xfs_bmapi_write that covers
    an existing delayed allocation.  As far as I can tell we do not have
    any other such caller, though - the regular writeback path uses
    xfs_bmapi_convert_delalloc to convert delayed allocations to real ones,
    and direct I/O invalidates the page cache first.
    Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
    Reviewed-by: default avatar"Darrick J. Wong" <djwong@kernel.org>
    Signed-off-by: default avatarChandan Babu R <chandanbabu@kernel.org>
    35dc55b9
xfs_bmap_util.c 48.4 KB