From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@osdl.org, akpm@linux-foundation.org,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org,
Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Subject: Re: [PATCH] AFS: Fix compilation warning
Date: Tue, 14 Jul 2009 14:28:51 +0530 [thread overview]
Message-ID: <1247561931.2473.2.camel@ht.satnam> (raw)
In-Reply-To: <1247561220.2473.0.camel@ht.satnam>
On Tue, 2009-07-14 at 14:17 +0530, Jaswinder Singh Rajput wrote:
> On Thu, 2009-07-09 at 10:44 +0100, David Howells wrote:
> > From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> >
> > Fix the following warning:
> >
> > fs/afs/dir.c: In function 'afs_d_revalidate':
> > fs/afs/dir.c:567: warning: 'fid.vnode' may be used uninitialized in this function
> > fs/afs/dir.c:567: warning: 'fid.unique' may be used uninitialized in this function
> >
> > by marking the 'fid' variable as an uninitialized_var. The problem is that gcc
> > doesn't always manage to work out that fid is always set on the path through
> > the function that uses it.
> >
> > Cc: linux-afs@lists.infradead.org
> > Cc: linux-kernel@vger.kernel.org
> > Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> > Signed-off-by: David Howells <dhowells@redhat.com>
> > ---
> >
>
> Have you tried this approach :
>
> diff --git a/fs/afs/dir.c b/fs/afs/dir.c
> index 9bd7577..09cb5bb 100644
> --- a/fs/afs/dir.c
> +++ b/fs/afs/dir.c
> @@ -607,53 +607,56 @@ static int afs_d_revalidate(struct dentry *dentry, struct nameidata *nd)
>
> /* search the directory for this vnode */
> ret = afs_do_lookup(&dir->vfs_inode, dentry, &fid, key);
> - switch (ret) {
> - case 0:
> - /* the filename maps to something */
> - if (!dentry->d_inode)
> - goto out_bad;
> - if (is_bad_inode(dentry->d_inode)) {
> - printk("kAFS: afs_d_revalidate: %s/%s has bad inode\n",
> - parent->d_name.name, dentry->d_name.name);
> + if (ret < 0) {
> + switch (ret) {
> + case -ENOENT:
> + /* the filename is unknown */
> + _debug("%s: dirent not found", dentry->d_name.name);
> + if (dentry->d_inode)
> + goto not_found;
> + goto out_valid;
> +
> + default:
> + _debug("failed to iterate dir %s: %d",
> + parent->d_name.name, ret);
> goto out_bad;
> }
> + }
>
> - /* if the vnode ID has changed, then the dirent points to a
> - * different file */
> - if (fid.vnode != vnode->fid.vnode) {
> - _debug("%s: dirent changed [%u != %u]",
> - dentry->d_name.name, fid.vnode,
> - vnode->fid.vnode);
> - goto not_found;
> - }
> -
> - /* if the vnode ID uniqifier has changed, then the file has
> - * been deleted and replaced, and the original vnode ID has
> - * been reused */
> - if (fid.unique != vnode->fid.unique) {
> - _debug("%s: file deleted (uq %u -> %u I:%llu)",
> - dentry->d_name.name, fid.unique,
> - vnode->fid.unique,
> - (unsigned long long)dentry->d_inode->i_version);
> - spin_lock(&vnode->lock);
> - set_bit(AFS_VNODE_DELETED, &vnode->flags);
> - spin_unlock(&vnode->lock);
> - goto not_found;
> - }
> - goto out_valid;
> -
> - case -ENOENT:
> - /* the filename is unknown */
> - _debug("%s: dirent not found", dentry->d_name.name);
> - if (dentry->d_inode)
> - goto not_found;
> - goto out_valid;
> -
> - default:
> - _debug("failed to iterate dir %s: %d",
> - parent->d_name.name, ret);
> + /* the filename maps to something */
> + if (!dentry->d_inode)
> goto out_bad;
> + if (is_bad_inode(dentry->d_inode)) {
> + printk("kAFS: afs_d_revalidate: %s/%s has bad inode\n",
> + parent->d_name.name, dentry->d_name.name);
> + goto out_bad;
> + }
> +
> + /*
> + * if the vnode ID has changed, then the dirent points to a
> + * different file
> + */
> + if (fid.vnode != vnode->fid.vnode) {
> + _debug("%s: dirent changed [%u != %u]",
> + dentry->d_name.name, fid.vnode, vnode->fid.vnode);
> + goto not_found;
> + }
> +
> + /*
> + * if the vnode ID uniqifier has changed, then the file has been
> + * deleted and replaced, and the original vnode ID has been reused
> + */
> + if (fid.unique != vnode->fid.unique) {
> + _debug("%s: file deleted (uq %u -> %u I:%llu)",
> + dentry->d_name.name, fid.unique,
> + vnode->fid.unique,
> + (unsigned long long)dentry->d_inode->i_version);
> + spin_lock(&vnode->lock);
> + set_bit(AFS_VNODE_DELETED, &vnode->flags);
> + spin_unlock(&vnode->lock);
> + goto not_found;
> }
> + goto out_valid;
You can also remove this goto. So by this way, you can get rid of :
1. compiler warning
2. fix 80 column wrap problem
3. remove one goto
Enjoy.
--
JSR
next prev parent reply other threads:[~2009-07-14 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 9:44 [PATCH] AFS: Fix compilation warning David Howells
2009-07-14 8:47 ` Jaswinder Singh Rajput
2009-07-14 8:58 ` Jaswinder Singh Rajput [this message]
2009-07-14 13:10 ` David Howells
2009-07-14 13:49 ` Jaswinder Singh Rajput
2009-07-14 14:16 ` David Howells
2009-07-14 16:17 ` David Howells
2009-07-14 16:36 ` Artem Bityutskiy
2009-07-14 17:22 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2009-07-09 8:04 [PATCH] AFS: fix " Artem Bityutskiy
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=1247561931.2473.2.camel@ht.satnam \
--to=jaswinder@kernel.org \
--cc=Artem.Bityutskiy@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.