From: Jesper Juhl <jesper.juhl@gmail.com>
To: David Rientjes <rientjes@cs.washington.edu>
Cc: linux-kernel@vger.kernel.org,
Andreas Gruenbacher <agruen@suse.de>,
Neil Brown <neilb@cse.unsw.edu.au>,
nfs@lists.sourceforge.net, Andrew Morton <akpm@osdl.org>,
Jesper Juhl <jesper.juhl@gmail.com>
Subject: Re: [PATCH] NFS: nfsaclsvc_encode_getaclres() - Fix potential NULL deref and tiny optimization.
Date: Sat, 28 Oct 2006 00:01:48 +0200 [thread overview]
Message-ID: <200610280001.49272.jesper.juhl@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0610271443500.31179@attu2.cs.washington.edu>
On Friday 27 October 2006 23:46, David Rientjes wrote:
> On Fri, 27 Oct 2006, Jesper Juhl wrote:
>
> > In fs/nfsd/nfs2acl.c::nfsaclsvc_encode_getaclres() I see a few issues.
> >
> > 1) At the top of the function we assign to the 'inode' variable by
> > dereferencing 'dentry', but further down we test 'dentry' for NULL. So, if
> > 'dentry' (which is really 'resp->fh.fh_dentry') can be NULL, then either
> > we have a potential NULL pointer deref bug or we have a superflous test.
> >
>
> resp->fh.fh_dentry cannot be NULL on nfsaclsvc_encode_getaclres so the
> early assignment is appropriate for both *dentry and *inode.
I didn't convince myself of that on my first scan of the code, that's why
I opted to keep the NULL check.
> *inode will
> need to be checked for NULL in the conditional, however, and return 0 on
> true.
>
Right, that agrees with my reading as well.
> > 3) There are two locations in the function where we may return before we
> > use the value of the variable 'w', but we compute it at the very top of the
> > function. So in the case where we return early we have wasted a few cycles
> > computing a value that was never used.
> >
>
> w should be an unsigned int.
>
Makes sense.
Thank you for commenting.
Here's a patch, on top of the previous one, to address you comments.
Feedback welcome.
Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
---
fs/nfsd/nfs2acl.c | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/fs/nfsd/nfs2acl.c b/fs/nfsd/nfs2acl.c
index d89d63f..069d7d0 100644
--- a/fs/nfsd/nfs2acl.c
+++ b/fs/nfsd/nfs2acl.c
@@ -222,14 +222,13 @@ static int nfsaclsvc_encode_getaclres(st
{
struct dentry *dentry = resp->fh.fh_dentry;
struct kvec *head = rqstp->rq_res.head;
- struct inode *inode;
+ struct inode *inode = dentry->d_inode;
unsigned int base;
- int w;
+ unsigned int w;
int n;
- if (dentry == NULL || dentry->d_inode == NULL)
+ if (!inode)
return 0;
- inode = dentry->d_inode;
p = nfs2svc_encode_fattr(rqstp, p, &resp->fh);
*p++ = htonl(resp->mask);
next prev parent reply other threads:[~2006-10-27 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 21:16 [PATCH] NFS: nfsaclsvc_encode_getaclres() - Fix potential NULL deref and tiny optimization Jesper Juhl
2006-10-27 21:46 ` David Rientjes
2006-10-27 22:01 ` Jesper Juhl [this message]
2006-10-31 16:26 ` Andreas Gruenbacher
2006-10-31 16:40 ` Jesper Juhl
2006-10-31 20:39 ` David Rientjes
2006-11-02 15:07 ` Andreas Gruenbacher
2006-10-31 20:39 ` Small optimization for nfs3acl. (was: Re: [PATCH] NFS: nfsaclsvc_encode_getaclres() - Fix potential NULL deref and tiny optimization.) Jesper Juhl
2006-11-02 15:06 ` Andreas Gruenbacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200610280001.49272.jesper.juhl@gmail.com \
--to=jesper.juhl@gmail.com \
--cc=agruen@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=rientjes@cs.washington.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox