diff options
author | Yihao Wu <wuyihao@linux.alibaba.com> | 2019-05-13 14:58:22 +0800 |
---|---|---|
committer | Anna Schumaker <Anna.Schumaker@Netapp.com> | 2019-05-30 15:51:07 -0400 |
commit | ba851a39c9703f09684a541885ed176f8fb7c868 (patch) | |
tree | d3b3da1cb56a5fac1005fadccd3b391e7ab2ee76 /fs/nfs/nfs4super.c | |
parent | 52b042ab9948cc367b61f9ca9c18603aa7813c3a (diff) | |
download | linux-ba851a39c9703f09684a541885ed176f8fb7c868.tar.bz2 |
NFSv4.1: Fix bug only first CB_NOTIFY_LOCK is handled
When a waiter is waked by CB_NOTIFY_LOCK, it will retry
nfs4_proc_setlk(). The waiter may fail to nfs4_proc_setlk() and sleep
again. However, the waiter is already removed from clp->cl_lock_waitq
when handling CB_NOTIFY_LOCK in nfs4_wake_lock_waiter(). So any
subsequent CB_NOTIFY_LOCK won't wake this waiter anymore. We should
put the waiter back to clp->cl_lock_waitq before retrying.
Cc: stable@vger.kernel.org #4.9+
Signed-off-by: Yihao Wu <wuyihao@linux.alibaba.com>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'fs/nfs/nfs4super.c')
0 files changed, 0 insertions, 0 deletions