ext4: truncate the file properly if we fail to copy data from userspace

Browse source

In generic_perform_write if we fail to copy the user data we don't
update the inode->i_size.  We should truncate the file in the above
case so that we don't have blocks allocated outside inode->i_size.  Add
the inode to orphan list in the same transaction as block allocation
This ensures that if we crash in between the recovery would do the
truncate.

Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
CC:  Jan Kara <jack@suse.cz>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>

...

This commit is contained in:

Aneesh Kumar K.V 2009-06-05 00:56:49 -04:00 • committed by Theodore Ts'o

parent 1938a150c2

commit f8514083cd

1 changed files with 102 additions and 26 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

128

fs/ext4/inode.c

View file