[PATCH 19/22] lockd: fix use of h_nextrebind

[PATCH 19/22] lockd: fix use of h_nextrebind

[Olaf Kirch]

From: Olaf Kirch <okir@suse.de>
Subject: lockd: fix use of h_nextrebind

  nlmclnt_recovery would try to force a portmap rebind by setting
  host->h_nextrebind to 0. The right thing to do here is to set it
  to the current time.

Signed-off-by: okir@suse.de

 fs/lockd/clntlock.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

Index: build/fs/lockd/clntlock.c
===================================================================
--- build.orig/fs/lockd/clntlock.c
+++ build/fs/lockd/clntlock.c
@@ -187,7 +187,7 @@ restart:
 	/* Force a portmap getport - the peer's lockd will
 	 * most likely end up on a different port.
 	 */
-	host->h_nextrebind = 0;
+	host->h_nextrebind = jiffies;
 	nlm_rebind_host(host);
 
 	/* First, reclaim all locks that have been granted. */

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs