ext3: Fix data / filesystem corruption when write fails to copy data
authorJan Kara <jack@suse.cz>
Tue, 1 Dec 2009 15:53:06 +0000 (16:53 +0100)
committerJan Kara <jack@suse.cz>
Thu, 10 Dec 2009 14:02:55 +0000 (15:02 +0100)
commit68eb3db08344286733adac48304d9fb7a0e53b27
tree214133860fdb6ceac4adbeb621837df8c494f1fb
parent5a20bdfcdc5c5e5f0647d8d99a998066ef5496ac
ext3: Fix data / filesystem corruption when write fails to copy data

When ext3_write_begin fails after allocating some blocks or
generic_perform_write fails to copy data to write, we truncate blocks already
instantiated beyond i_size. Although these blocks were never inside i_size, we
have to truncate pagecache of these blocks so that corresponding buffers get
unmapped. Otherwise subsequent __block_prepare_write (called because we are
retrying the write) will find the buffers mapped, not call ->get_block, and
thus the page will be backed by already freed blocks leading to filesystem and
data corruption.

Reported-by: James Y Knight <foom@fuhm.net>
Signed-off-by: Jan Kara <jack@suse.cz>
fs/ext3/inode.c