NFS: initialize flags field in nfs_open_context

The nfs_open_context struct had a "flags" field added recently, but the allocator isn't initializing it. It also looks like the allocator isn't initializing the mode or list either, but they seem to be overwritten by the caller, so that's less of an issue. Signed-off-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

NFS: initialize flags field in nfs_open_context
The nfs_open_context struct had a "flags" field added recently, but the allocator isn't initializing it. It also looks like the allocator isn't initializing the mode or list either, but they seem to be overwritten by the caller, so that's less of an issue. Signed-off-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Jeff Layton · Trond Myklebust
1 parent daeba89d43
Showing 1 changed file with 1 additions and 0 deletions Side-by-side Diff
fs/nfs/inode.c
@@ -506,6 +506,7 @@
 		ctx->cred = get_rpccred(cred);
 		ctx->state = NULL;
 		ctx->lockowner = current->files;
+		ctx->flags = 0;
 		ctx->error = 0;
 		ctx->dir_cookie = 0;
 		atomic_set(&ctx->count, 1);
...	...	@@ -506,6 +506,7 @@
506	506	ctx->cred = get_rpccred(cred);
507	507	ctx->state = NULL;
508	508	ctx->lockowner = current->files;
	509	+ ctx->flags = 0;
509	510	ctx->error = 0;
510	511	ctx->dir_cookie = 0;
511	512	atomic_set(&ctx->count, 1);