Yunchuan Wen f1fc4fee3b ceph: fscache: Wait for completion of object initialization ... The object store limit needs to be updated after writing, and this can be done provided the corresponding object has already been initialized. Current object initialization is done asynchrously, which introduce a race if a file is opened, then immediately followed by a writing, the initialization may have not completed, the code will reach the ASSERT in fscache_submit_exclusive_op() to cause kernel bug. Tested-by: Milosz Tanski <milosz@adfin.com> Signed-off-by: Yunchuan Wen <yunchuanwen@ubuntukylin.com> Signed-off-by: Min Chen <minchen@ubuntukylin.com> Signed-off-by: Li Wang <liwang@ubuntukylin.com>		2014-04-03 10:33:53 +08:00
..
acl.c
addr.c
cache.c	ceph: fscache: Wait for completion of object initialization	2014-04-03 10:33:53 +08:00
cache.h	ceph: fscache: add an interface to synchronize object store limit	2014-04-03 10:33:53 +08:00
caps.c
ceph_frag.c
debugfs.c	ceph: do not assume r_old_dentry[_dir] always set together	2014-04-03 10:33:53 +08:00
dir.c	ceph: do not set r_old_dentry_dir on link()	2014-04-03 10:33:53 +08:00
export.c
file.c	ceph: fscache: Update object store limit after file writing	2014-04-03 10:33:53 +08:00
inode.c	ceph: do not chain inode updates to parent fsync	2014-04-03 10:33:52 +08:00
ioctl.c	ceph: do not chain inode updates to parent fsync	2014-04-03 10:33:52 +08:00
ioctl.h
Kconfig
locks.c
Makefile
mds_client.c	ceph: do not assume r_old_dentry[_dir] always set together	2014-04-03 10:33:53 +08:00
mds_client.h
mdsmap.c
snap.c
strings.c
super.c
super.h
xattr.c	ceph: do not chain inode updates to parent fsync	2014-04-03 10:33:52 +08:00