aboutsummaryrefslogtreecommitdiffstats
path: root/fs/gfs2
diff options
context:
space:
mode:
authorWendy Cheng <wcheng@redhat.com>2007-06-27 11:00:03 -0400
committerSteven Whitehouse <swhiteho@redhat.com>2007-07-09 03:23:59 -0400
commit090ffaa55dacea774af9ee378d09e47fb7cea9ff (patch)
tree5482762609a8c2e3a312434eb7e997e5b72912f3 /fs/gfs2
parent97d848365e603def43c69e160937f073bf9cf02e (diff)
[GFS2] inode size inconsistency
This should have been part of the NFS patch #1 but somehow I missed it when packaging the patches. It is not a critical issue as the others (I hope). RHEL 5.1 31.el5 kernel runs fine without this change. Our truncate code is chopped into two parts, one for vfs inode changes (in vmtruncate()) and one of gfs inode (in gfs2_truncatei()). These two operatons are, unfortunately, not atomic. So it could happens that vmtruncate() succeeds (inode->i_size is changed) but gfs2_truncatei fails (say kernel temporarily out of memory). This would leave gfs inode i_di.di_size out of sync with vfs inode i_size. It will later confuse gfs2_commit_write() if a write is issued. Last time I checked, it will cause file corruption. Signed-off-by: S. Wendy Cheng <wcheng@redhat.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'fs/gfs2')
-rw-r--r--fs/gfs2/ops_inode.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/gfs2/ops_inode.c b/fs/gfs2/ops_inode.c
index 84051b997a43..911c115b5c6c 100644
--- a/fs/gfs2/ops_inode.c
+++ b/fs/gfs2/ops_inode.c
@@ -903,8 +903,8 @@ static int setattr_size(struct inode *inode, struct iattr *attr)
903 } 903 }
904 904
905 error = gfs2_truncatei(ip, attr->ia_size); 905 error = gfs2_truncatei(ip, attr->ia_size);
906 if (error) 906 if (error && (inode->i_size != ip->i_di.di_size))
907 return error; 907 i_size_write(inode, ip->i_di.di_size);
908 908
909 return error; 909 return error;
910} 910}