NFS: initialize nfs_open_context.list member at allocation time
Subsystems (2)
PATCH 1/1 NFS: initialize nfs_open_context.list member at allocation time
alloc_nfs_open_context creates a nfs_open_context struct, but doesn't initialize the list_head embedded in it. In newer kernels, this is harmless since the ctx is always put on a list soon after creation. In an older RHEL4 kernel however, it's possible (though unlikely) for a ctx to be passed to put_nfs_open_context without ever being put on a list, which can cause an oops.
Since it's hard to predict how this code will change in the future, let's go ahead and initialize the list.
--- fs/nfs/inode.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
fs/nfs/inode.c +1 -0
@@ -638,6 +638,7 @@ static struct nfs_open_context *alloc_nfs_open_context(struct path *path, struct ctx->dir_cookie =0 ;nfs_init_lock_context (&ctx->lock_context); ctx->lock_context.open_context = ctx; +INIT_LIST_HEAD (&ctx->list); }return ctx; }
Signature · 1 line
1.7.1
Quoted 21 lines · Jeff Layton
alloc_nfs_open_contextcreates anfs_open_contextstruct, but doesn't initialize thelist_headembedded in it. In newer kernels, this is harmless since the ctx is always put on a list soon after creation. In an older RHEL4 kernel however, it's possible (though unlikely) for a ctx to be passed toput_nfs_open_contextwithout ever being put on a list, which can cause an oops.Since it's hard to predict how this code will change in the future, let's go ahead and initialize the list.
Reported-by Paul Bunyan <[email protected]>Signed-off-by Jeff Layton <[email protected]>--- fs/nfs/inode.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)fs/nfs/inode.c +0
-0
fs/nfs/inode.c static struct nfs_open_context *alloc_nfs_open_context(struct path *path, struct · line 644
Quoted 7 lines
fs/nfs/inode.c +1
-0@@ -638,6 +638,7 @@ static struct nfs_open_context *alloc_nfs_open_context(struct path *path, struct ctx->dir_cookie =0 ;nfs_init_lock_context (&ctx->lock_context); ctx->lock_context.open_context = ctx; +INIT_LIST_HEAD (&ctx->list); }return ctx; }
Hi Jeff,
I'm really too keen to merge stuff into 2.6.37 with the sole justification being that it is needed to keep kernel 2.6.9 in sync.
That said, you appear to be in luck today: I found a reason to apply something like the above in 2.6.37 too. Please see the patch below, that appears to need to be applied to the nfs-for-2.6.37 branch.
Cheers
Trond
-------------------------------------------------------------------------------------------
commit 2128d32b4fbb85bba129ca7b6d4c8e118d4a325b
Author: Trond Myklebust <[email protected]> Date: Mon Sep 27 15:51:20 2010 -0400
NFS: Really fix put_nfs_open_context()
In nfs_open_revalidate(), if the open_context() call returns an inode that is not the same as dentry->d_inode, then we will call put_nfs_open_context() with a valid dentry->d_inode, but without the context being part of the nfsi->open_files list.
In this case too, we want to just skip the list removal, but we do want to call the ->close_context() callback in order to close the NFSv4 state.
fs/nfs/inode.c +4 -2
@@ -635,6 +635,7 @@ struct nfs_open_context *alloc_nfs_open_context(struct path *path, struct rpc_cr ctx->dir_cookie =0 ;nfs_init_lock_context (&ctx->lock_context); ctx->lock_context.open_context = ctx; +INIT_LIST_HEAD (&ctx->list); }return ctx; }
@@ -650,14 +651,15 @@ static void __put_nfs_open_context(struct nfs_open_context *ctx, int is_sync) {struct inode *inode = ctx->path.dentry->d_inode; -if (inode) { +if (!list_empty (&ctx->list)) {if (!atomic_dec_and_lock (&ctx->lock_context.count, &inode->i_lock))return ;list_del (&ctx->list);spin_unlock (&inode->i_lock); -NFS_PROTO (inode)->close_context (ctx, is_sync); }else if (!atomic_dec_and_test (&ctx->lock_context.count))return ; +if (inode !=NULL ) +NFS_PROTO (inode)->close_context (ctx, is_sync);if (ctx->cred !=NULL )put_rpccred (ctx->cred);path_put (&ctx->path);
Jeff Layton
Acked-byQuoted 79 lines · On Mon, 27 Sep 2010 16:09:59 -0400 Trond Myklebust…
Quoted 21 lines · Jeff Layton
alloc_nfs_open_contextcreates anfs_open_contextstruct, but doesn't initialize thelist_headembedded in it. In newer kernels, this is harmless since the ctx is always put on a list soon after creation. In an older RHEL4 kernel however, it's possible (though unlikely) for a ctx to be passed toput_nfs_open_contextwithout ever being put on a list, which can cause an oops.Since it's hard to predict how this code will change in the future, let's go ahead and initialize the list.
Reported-by Paul Bunyan <[email protected]>Signed-off-by Jeff Layton <[email protected]>--- fs/nfs/inode.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)fs/nfs/inode.c +0
-0fs/nfs/inode.c static struct nfs_open_context *alloc_nfs_open_context(struct path *path, struct · line 644
Quoted 7 lines
fs/nfs/inode.c +1
-0@@ -638,6 +638,7 @@ static struct nfs_open_context *alloc_nfs_open_context(struct path *path, struct ctx->dir_cookie =0 ;nfs_init_lock_context (&ctx->lock_context); ctx->lock_context.open_context = ctx; +INIT_LIST_HEAD (&ctx->list); }return ctx; }Hi Jeff,
I'm really too keen to merge stuff into 2.6.37 with the sole justification being that it is needed to keep kernel 2.6.9 in sync.
That said, you appear to be in luck today: I found a reason to apply something like the above in 2.6.37 too. Please see the patch below, that appears to need to be applied to the nfs-for-2.6.37 branch.
Cheers
Trond
-------------------------------------------------------------------------------------------
commit2128d32b4fbb85bba129ca7b6d4c8e118d4a325bAuthor: Trond Myklebust <[email protected]> Date: Mon Sep 27 15:51:20 2010 -0400NFS: Really fix
put_nfs_open_context()In
nfs_open_revalidate(), if theopen_context()call returns an inode that is not the same asdentry->d_inode, then we will callput_nfs_open_context()with a validdentry->d_inode, but without the context being part of thenfsi->open_fileslist.In this case too, we want to just skip the list removal, but we do want to call the ->close_context() callback in order to close the NFSv4 state.
Signed-off-by Trond Myklebust <[email protected]>fs/nfs/inode.c +2
-1@@ -635,6 +635,7 @@ struct nfs_open_context *alloc_nfs_open_context(struct path *path, struct rpc_cr ctx->dir_cookie =0 ;nfs_init_lock_context (&ctx->lock_context); ctx->lock_context.open_context = ctx; +INIT_LIST_HEAD (&ctx->list); }return ctx; }@@ -650,14 +651,15 @@ static void __put_nfs_open_context(struct nfs_open_context *ctx, int is_sync) {struct inode *inode = ctx->path.dentry->d_inode; -if (inode) { +if (!list_empty (&ctx->list)) {if (!atomic_dec_and_lock (&ctx->lock_context.count, &inode->i_lock))return ;
fs/nfs/inode.c static void __put_nfs_open_context(struct nfs_open_context *ctx, int is_sync) · line 665
Quoted 10 lines
fs/nfs/inode.c +2
-1list_del (&ctx->list);spin_unlock (&inode->i_lock); -NFS_PROTO (inode)->close_context (ctx, is_sync); }else if (!atomic_dec_and_test (&ctx->lock_context.count))return ; +if (inode !=NULL ) +NFS_PROTO (inode)->close_context (ctx, is_sync);if (ctx->cred !=NULL )put_rpccred (ctx->cred);path_put (&ctx->path);
Thanks, Trond. For the record, my concern here was more for the "defensive coding" aspect rather than a desire to keep RHEL4 in sync with upstream (which is really, really a lost cause).
Patch looks good to me.