summaryrefslogtreecommitdiffstats
path: root/kernel/semaphore.c
diff options
context:
space:
mode:
authorYan, Zheng <zheng.z.yan@intel.com>2013-07-02 12:40:20 +0800
committerSage Weil <sage@inktank.com>2013-07-03 15:32:57 -0700
commitb1530f57042297f85330a140a6921b6f95fe74d3 (patch)
tree0af45d94a71bd69d59aa0d2399a5c06623d9170c /kernel/semaphore.c
parentb415bf4f9fe25f39934f5c464125e4a2dffb6d08 (diff)
downloadop-kernel-dev-b1530f57042297f85330a140a6921b6f95fe74d3.zip
op-kernel-dev-b1530f57042297f85330a140a6921b6f95fe74d3.tar.gz
ceph: fix cap revoke race
If caps are been revoking by the auth MDS, don't consider them as issued even they are still issued by non-auth MDS. The non-auth MDS should also be revoking/exporting these caps, the client just hasn't received the cap revoke/export message. The race I encountered is: When caps are exporting to new MDS, the client receives cap import message and cap revoke message from the new MDS, then receives cap export message from the old MDS. When the client receives cap revoke message from the new MDS, the revoking caps are still issued by the old MDS, so the client does nothing. Later when the cap export message is received, the client removes the caps issued by the old MDS. (Another way to fix the race is calling ceph_check_caps() in handle_cap_export()) Signed-off-by: Yan, Zheng <zheng.z.yan@intel.com> Reviewed-by: Sage Weil <sage@inktank.com>
Diffstat (limited to 'kernel/semaphore.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud