• Mark Fasheh's avatar
    ocfs2: Write support for inline data · 1afc32b9
    Mark Fasheh authored
    This fixes up write, truncate, mmap, and RESVSP/UNRESVP to understand inline
    inode data.
    
    For the most part, the changes to the core write code can be relied on to do
    the heavy lifting. Any code calling ocfs2_write_begin (including shared
    writeable mmap) can count on it doing the right thing with respect to
    growing inline data to an extent tree.
    
    Size reducing truncates, including UNRESVP can simply zero that portion of
    the inode block being removed. Size increasing truncatesm, including RESVP
    have to be a little bit smarter and grow the inode to an extent tree if
    necessary.
    Signed-off-by: default avatarMark Fasheh <mark.fasheh@oracle.com>
    Reviewed-by: default avatarJoel Becker <joel.becker@oracle.com>
    1afc32b9
inode.c 34.5 KB