NFS: Avoid infinite loop when RELEASE_LOCKOWNER getting expired error
authorKinglong Mee <kinglongmee@gmail.com>
Mon, 4 Aug 2014 08:18:16 +0000 (16:18 +0800)
committerTrond Myklebust <trond.myklebust@primarydata.com>
Mon, 4 Aug 2014 20:51:38 +0000 (16:51 -0400)
commit5b53dc88b064cb93274e7fb81f8df477287c80df
tree94b3eff48b9e917ec2ce9f7ffa3b2a93b3293372
parent122a8cda6a9a3594c4737570f5cd81636bcd20cf
NFS: Avoid infinite loop when RELEASE_LOCKOWNER getting expired error

Fix Commit 60ea681299 (NFS: Migration support for RELEASE_LOCKOWNER)
If getting expired error, client will enter a infinite loop as,

client                            server
   RELEASE_LOCKOWNER(old clid) ----->
                <--- expired error
   RENEW(old clid)             ----->
                <--- expired error
   SETCLIENTID                 ----->
                <--- a new clid
   SETCLIENTID_CONFIRM (new clid) -->
                <--- ok
   RELEASE_LOCKOWNER(old clid) ----->
                <--- expired error
   RENEW(new clid)             ----->
                <-- ok
   RELEASE_LOCKOWNER(old clid) ----->
                <--- expired error
   RENEW(new clid)             ----->
                <-- ok
                ... ...

Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
[Trond: replace call to nfs4_async_handle_error() with
 nfs4_schedule_lease_recovery()]
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
fs/nfs/nfs4proc.c