Jan Kara 156bddd8e5 ext3: Fix fdatasync() for files with only i_size changes ... Code tracking when transaction needs to be committed on fdatasync(2) forgets to handle a situation when only inode's i_size is changed. Thus in such situations fdatasync(2) doesn't force transaction with new i_size to disk and that can result in wrong i_size after a crash. Fix the issue by updating inode's i_datasync_tid whenever its size is updated. CC: <stable@vger.kernel.org> # >= 2.6.32 Reported-by: Kristian Nielsen <knielsen@knielsen-hq.org> Signed-off-by: Jan Kara <jack@suse.cz>		2012-09-04 00:04:43 +02:00
..
acl.c
acl.h
balloc.c	ext3: use memweight()	2012-07-30 17:25:16 -07:00
bitmap.c	ext3: use memweight()	2012-07-30 17:25:16 -07:00
dir.c	ext3: pass custom EOF to generic_file_llseek_size()	2012-07-23 00:00:30 +04:00
ext3_jbd.c
ext3.h
file.c
fsync.c
hash.c
ialloc.c
inode.c	ext3: Fix fdatasync() for files with only i_size changes	2012-09-04 00:04:43 +02:00
ioctl.c
Kconfig
Makefile
namei.c	don't expose I_NEW inodes via dentry->d_inode	2012-07-23 00:00:58 +04:00
namei.h
resize.c
super.c	ext3: nuke write_super from comments	2012-08-04 12:15:32 +04:00
symlink.c
xattr_security.c
xattr_trusted.c
xattr_user.c
xattr.c
xattr.h