git.stricted.de - GitHub/LineageOS/android_kernel_motorola

author	Dmitry Monakhov <dmonakhov@openvz.org>
	Thu, 13 Jun 2013 02:38:04 +0000 (22:38 -0400)
committer	Theodore Ts'o <tytso@mit.edu>
	Thu, 13 Jun 2013 02:38:04 +0000 (22:38 -0400)
commit	4418e14112e3ca85e8492a4489a3552b0cc526a8
tree	93abfabff161cc2f5b09d7aaf6aa4ae09ba13c7b	tree \| snapshot (tar.gz zip)
parent	06a407f13daf9e48f0ef7189c7e54082b53940c7	commit \| diff

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>

fs/ext4/fsync.c		diff \| blob \| blame \| history
fs/ext4/super.c		diff \| blob \| blame \| history