tree c914afd0ef5d32b426c3cf65820de7599e570656
parent 6798d35a31c413bbb3f83bbaa844bd2598168ccc
author Mark Fasheh <mark.fasheh@oracle.com> 1189201611 -0700
committer Mark Fasheh <mark.fasheh@oracle.com> 1192215280 -0700

ocfs2: Write support for inline data

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: Mark Fasheh <mark.fasheh@oracle.com>
Reviewed-by: Joel Becker <joel.becker@oracle.com>