[1/3] nfs4: always reset notified flag to false before repolling for lock
diff mbox

Message ID 20180318123703.11256-2-jlayton@kernel.org
State New
Headers show

Commit Message

Jeff Layton March 18, 2018, 12:37 p.m. UTC
From: Jeff Layton <jlayton@redhat.com>

We may get a notification and lose the race to another client. Ensure
that we wait again for a notification in that case.

Signed-off-by: Jeff Layton <jlayton@redhat.com>
 fs/nfs/nfs4proc.c | 1 +
 1 file changed, 1 insertion(+)

diff mbox

diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index 47f3c273245e..5ab28454f117 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -6673,6 +6673,7 @@  nfs4_retry_setlk(struct nfs4_state *state, int cmd, struct file_lock *request)
 	add_wait_queue(q, &wait);
 	while(!signalled()) {
+		waiter.notified = false;
 		status = nfs4_proc_setlk(state, cmd, request);
 		if ((status != -EAGAIN) || IS_SETLK(cmd))