diff options
author | Christoph Hellwig <hch@infradead.org> | 2010-06-14 05:17:31 -0400 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2010-08-09 16:47:42 -0400 |
commit | fa9b227e9019ebaeeb06224ba531a490f91144b3 (patch) | |
tree | ff3644c6572d2b22db0d8b71f1a79ae0ad33d102 /REPORTING-BUGS | |
parent | 2f246fd0f126f3b3c23a4e6b7109350e83356bd6 (diff) | |
download | kernel_samsung_espresso10-fa9b227e9019ebaeeb06224ba531a490f91144b3.zip kernel_samsung_espresso10-fa9b227e9019ebaeeb06224ba531a490f91144b3.tar.gz kernel_samsung_espresso10-fa9b227e9019ebaeeb06224ba531a490f91144b3.tar.bz2 |
xfs: new truncate sequence
Convert XFS to the new truncate sequence. We still can have errors after
updating the file size in xfs_setattr, but these are real I/O errors and lead
to a transaction abort and filesystem shutdown, so they are not an issue.
Errors from ->write_begin and write_end can now be handled correctly because
we can actually get rid of the delalloc extents while previous the buffer
state was stipped in block_invalidatepage.
There is still no error handling for ->direct_IO, because doing so will need
some major restructuring given that we only have the iolock shared and do not
hold i_mutex at all. Fortunately leaving the normally allocated blocks behind
there is not a major issue and this will get cleaned up by xfs_free_eofblock
later.
Note: the patch is against Al's vfs.git tree as that contains the nessecary
preparations. I'd prefer to get it applied there so that we can get some
testing in linux-next.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'REPORTING-BUGS')
0 files changed, 0 insertions, 0 deletions