[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090702203937.GA10504@fieldses.org>
Date: Thu, 2 Jul 2009 16:39:37 -0400
From: "J. Bruce Fields" <bfields@...ldses.org>
To: David Howells <dhowells@...hat.com>
Cc: steved@...hat.com, rasmus@...onsult.dk, linux-nfs@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] NFSD: Don't hold unrefcounted creds over call to
nfsd_setuser()
On Thu, Jul 02, 2009 at 02:35:32PM +0100, David Howells wrote:
> nfsd_open() gets an unrefcounted pointer to the current process's effective
> credentials at the top of the function, then calls nfsd_setuser() via
> fh_verify() - which may replace and destroy the current process's effective
> credentials - and then passes the unrefcounted pointer to dentry_open() - but
> the credentials may have been destroyed by this point.
>
> Instead, the value from current_cred() should be passed directly to
> dentry_open() as one of its arguments, rather than being cached in a variable.
Got it, thanks. How easy is it to hit this case? (Just wondering
whether to submit for stable.)
--b.
>
> Possibly fh_verify() should return the creds to use.
>
> Signed-off-by: David Howells <dhowells@...hat.com>
> ---
>
> fs/nfsd/vfs.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
>
> diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
> index 4145083..23341c1 100644
> --- a/fs/nfsd/vfs.c
> +++ b/fs/nfsd/vfs.c
> @@ -678,7 +678,6 @@ __be32
> nfsd_open(struct svc_rqst *rqstp, struct svc_fh *fhp, int type,
> int access, struct file **filp)
> {
> - const struct cred *cred = current_cred();
> struct dentry *dentry;
> struct inode *inode;
> int flags = O_RDONLY|O_LARGEFILE;
> @@ -733,7 +732,7 @@ nfsd_open(struct svc_rqst *rqstp, struct svc_fh *fhp, int type,
> vfs_dq_init(inode);
> }
> *filp = dentry_open(dget(dentry), mntget(fhp->fh_export->ex_path.mnt),
> - flags, cred);
> + flags, current_cred());
> if (IS_ERR(*filp))
> host_err = PTR_ERR(*filp);
> else
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists