[PATCH] nfs: check nf pointer for validity before use

* [PATCH] nfs: check nf pointer for validity before use
@ 2021-12-21 18:55 Muhammad Usama Anjum
  2021-12-21 20:00 ` Chuck Lever III
  2021-12-21 22:18 ` Konstantin Ryabitsev
  0 siblings, 2 replies; 4+ messages in thread
From: Muhammad Usama Anjum @ 2021-12-21 18:55 UTC (permalink / raw)
  To: J. Bruce Fields, Chuck Lever, Vasily Averin,
	open list:KERNEL NFSD, SUNRPC, AND LOCKD SERVERS, open list
  Cc: usama.anjum, kernel, kernel-janitors

Pointer nf can be NULL. It should be validated before dereferencing it.

Fixes: 8628027ba8 ("nfs: block notification on fs with its own ->lock")
Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
---
 fs/nfsd/nfs4state.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
index a526d4183348..bdd30988e615 100644
--- a/fs/nfsd/nfs4state.c
+++ b/fs/nfsd/nfs4state.c
@@ -6947,6 +6947,11 @@ nfsd4_lock(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
 		goto out;
 	}
 
+	if (!nf) {
+		status = nfserr_openmode;
+		goto out;
+	}
+
 	/*
 	 * Most filesystems with their own ->lock operations will block
 	 * the nfsd thread waiting to acquire the lock.  That leads to
@@ -6957,11 +6962,6 @@ nfsd4_lock(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
 	if (nf->nf_file->f_op->lock)
 		fl_flags &= ~FL_SLEEP;
 
-	if (!nf) {
-		status = nfserr_openmode;
-		goto out;
-	}
-
 	nbl = find_or_allocate_block(lock_sop, &fp->fi_fhandle, nn);
 	if (!nbl) {
 		dprintk("NFSD: %s: unable to allocate block!\n", __func__);
-- 
2.30.2


^ permalink raw reply related	[flat|nested] 4+ messages in thread