|author||Sage Weil <firstname.lastname@example.org>||2010-10-27 20:59:49 -0700|
|committer||Sage Weil <email@example.com>||2010-10-27 21:05:54 -0700|
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 <firstname.lastname@example.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions