Dmitry Monakhov 4418e14112 ext4: Fix fsync error handling after filesystem abort
If filesystem was aborted after inode's write back is complete
but before its metadata was updated we may return success
results in data loss.
In order to handle fs abort correctly we have to check
fs state once we discover that it is in MS_RDONLY state

Test case: http://patchwork.ozlabs.org/patch/244297

Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2013-06-12 22:38:04 -04:00
..
2011-07-25 14:30:23 -04:00
2013-06-06 11:40:37 -04:00
2013-05-03 02:15:52 -04:00
2013-05-03 02:15:52 -04:00
2013-04-09 22:48:36 -04:00
2012-12-10 16:30:43 -05:00
2012-12-10 16:30:43 -05:00