Christoph Hellwig 26821ed40b make sure data is on disk before calling ->write_inode ... Similar to the fsync issue fixed a while ago in commit 2daea67e96 we need to write for data to actually hit the disk before writing out the metadata to guarantee data integrity for filesystems that modify the inode in the data I/O completion path. Currently XFS and NFS handle this manually, and AFS has a write_inode method that does nothing but waiting for data, while others are possibly missing out on this. Fortunately this change has a lot less impact than the fsync change as none of the write_inode methods starts data writeout of any form by itself. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>		2010-03-05 13:25:10 -05:00
..
afs_cm.h
afs_fs.h
afs_vl.h
afs.h
cache.c
callback.c
cell.c
cmservice.c
dir.c
file.c	FS-Cache: Handle pages pending storage that get evicted under OOM conditions	2009-11-19 18:11:35 +00:00
flock.c
fsclient.c
inode.c
internal.h	make sure data is on disk before calling ->write_inode	2010-03-05 13:25:10 -05:00
Kconfig
main.c
Makefile
misc.c
mntpt.c
netdevices.c
proc.c
rxrpc.c
security.c
server.c
super.c	make sure data is on disk before calling ->write_inode	2010-03-05 13:25:10 -05:00
vlclient.c
vlocation.c
vnode.c
volume.c
write.c	make sure data is on disk before calling ->write_inode	2010-03-05 13:25:10 -05:00