2.6.32-longterm review patch. If anyone has any objections, please let us know.

------------------From: Steven Whitehouse <swhiteho@redhat.com>

commit 1e72c0f7c40e665d2ed40014750fdd2fa9968bcf upstream.

Both of these functions contained confusing and in one caseduplicate code. This patch adds a new check in do_glock()so that we report -ENOENT if we are asked to sync a quotaentry which doesn't exist. Due to the previous patch this isnow reported correctly to userspace.

Also there are a few new comments, and I hope that the codeis easier to understand now.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>--- fs/gfs2/quota.c | 82 +++++++++++++++++--------------------------------------- 1 file changed, 26 insertions(+), 56 deletions(-)--- a/fs/gfs2/quota.c+++ b/fs/gfs2/quota.c@@ -15,7 +15,7 @@ * fuzziness in the current usage value of IDs that are being used on different * nodes in the cluster simultaneously. So, it is possible for a user on * multiple nodes to overrun their quota, but that overrun is controlable.- * Since quota tags are part of transactions, there is no need to a quota check+ * Since quota tags are part of transactions, there is no need for a quota check * program to be run on node crashes or anything like that. * * There are couple of knobs that let the administrator manage the quota@@ -65,13 +65,6 @@ #define QUOTA_USER 1 #define QUOTA_GROUP 0