From: Benny Halevy <bhalevy@primarydata.com>
Date: Fri, 30 May 2014 13:09:27 +0000 (-0400)
Subject: nfsd4: use recall_lock for delegation hashing
X-Git-Tag: omap-for-v3.16/fixes-against-rc1~67^2~12
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=931ee56c67573eb4e51c8a4e78598d965b8b059e;p=pandora-kernel.git

nfsd4: use recall_lock for delegation hashing

This fixes a bug in the handling of the fi_delegations list.

nfs4_setlease does not hold the recall_lock when adding to it. The
client_mutex is held, which prevents against concurrent list changes,
but nfsd_break_deleg_cb does not hold while walking it. New delegations
could theoretically creep onto the list while we're walking it there.

Signed-off-by: Benny Halevy <bhalevy@primarydata.com>
Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Cc: stable@vger.kernel.org
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
---

Reading git-diff-tree failed