Revert "ceph: update issue_seq on cap grant"
authorSage Weil <sage@newdream.net>
Thu, 28 Oct 2010 03:59:49 +0000 (20:59 -0700)
committerSage Weil <sage@newdream.net>
Thu, 28 Oct 2010 04:05:54 +0000 (21:05 -0700)
commit2f56f56ad991edd51ffd0baf1182245ee1277a04
treee4062e2bb1a92b487609cded256d5ede1a6eda90
parentefa4c1206eaff047c474af2136748a58eb8cc33b
Revert "ceph: update issue_seq on cap grant"

This reverts commit d91f2438d881514e4a923fd786dbd94b764a9440.

The intent of issue_seq is to distinguish between mds->client messages that
(re)create the cap and those that do not, which means we should _only_ be
updating that value in the create paths.  By updating it in handle_cap_grant,
we reset it to zero, which then breaks release.

The larger question is what workload/problem made me think it should be
updated here...

Signed-off-by: Sage Weil <sage@newdream.net>
fs/ceph/caps.c