summaryrefslogtreecommitdiffstats
path: root/lib/lzo
diff options
context:
space:
mode:
authorYihao Wu <wuyihao@linux.alibaba.com>2019-05-13 14:58:22 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-06-11 12:19:16 +0200
commit11f087841e8650fbe51d112a21b465ad0c35ca5f (patch)
tree3a3e5160245b9fa00d1cb623d250229675d4361f /lib/lzo
parentd1d8b49a1b041752af08da839ddb78dba7f37cab (diff)
downloadlinux-stable-11f087841e8650fbe51d112a21b465ad0c35ca5f.tar.gz
linux-stable-11f087841e8650fbe51d112a21b465ad0c35ca5f.tar.bz2
linux-stable-11f087841e8650fbe51d112a21b465ad0c35ca5f.zip
NFSv4.1: Fix bug only first CB_NOTIFY_LOCK is handled
commit ba851a39c9703f09684a541885ed176f8fb7c868 upstream. 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> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'lib/lzo')
0 files changed, 0 insertions, 0 deletions