From: Sage Weil <sage@newdream.net>
Date: Thu, 28 Oct 2010 03:59:49 +0000 (-0700)
Subject: Revert "ceph: update issue_seq on cap grant"
X-Git-Tag: v2.6.37-rc3~2^2~15
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2f56f56ad991edd51ffd0baf1182245ee1277a04;p=pandora-kernel.git

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>
---

Reading git-diff-tree failed