From: Jim Rees <rees@umich.edu>
To: Benny Halevy <bhalevy@tonian.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] Silence compiler warning
Date: Sun, 16 Oct 2011 22:36:57 -0400 [thread overview]
Message-ID: <20111017023657.GA19126@umich.edu> (raw)
In-Reply-To: <4E9B8B75.4040209@tonian.com>
Benny Halevy wrote:
On 2011-10-16 17:06, Jim Rees wrote:
> fs/nfs/callback_proc.c: In function ‘do_callback_layoutrecall’:
> fs/nfs/callback_proc.c:115:26: warning: ‘lo’ may be used uninitialized in this function
>
> No functional change. If no layout is found, we'll return before using
> "lo".
>
> Signed-off-by: Jim Rees <rees@umich.edu>
> ---
> fs/nfs/callback_proc.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/nfs/callback_proc.c b/fs/nfs/callback_proc.c
> index 43926ad..93633f1 100644
> --- a/fs/nfs/callback_proc.c
> +++ b/fs/nfs/callback_proc.c
> @@ -112,7 +112,7 @@ static u32 initiate_file_draining(struct nfs_client *clp,
> struct cb_layoutrecallargs *args)
> {
> struct nfs_server *server;
> - struct pnfs_layout_hdr *lo;
> + struct pnfs_layout_hdr *lo = NULL;
> struct inode *ino;
> bool found = false;
> u32 rv = NFS4ERR_NOMATCHING_LAYOUT;
Hmm, the warning seems bogus since we use lo only iff found==true
and it is set iff found==true
I wonder why I don't see that warning.
What compiler/version are you using?
gcc (Ubuntu/Linaro 4.5.2-8ubuntu4) 4.5.2
I don't remember seeing this warning before either, but I can't think what I
might have changed that would make a difference. I did turn on SMP, which I
didn't have before (non-SMP kernels don't seem to work on the latest
Virtualbox). And yes, the warning is bogus, but should be fixed anyway.
next prev parent reply other threads:[~2011-10-17 2:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 0:06 [PATCH] Silence compiler warning Jim Rees
2011-10-17 1:57 ` Benny Halevy
2011-10-17 2:36 ` Jim Rees [this message]
2011-10-18 9:50 ` Stanislav Kinsbursky
-- strict thread matches above, loose matches on Subject: below --
2011-10-18 13:07 Benny Halevy
2011-11-01 1:37 Jim Rees
2011-11-01 2:30 ` Trond Myklebust
2011-11-01 2:42 ` Jim Rees
2011-11-01 2:56 ` Trond Myklebust
2011-11-01 3:01 ` Jim Rees
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=20111017023657.GA19126@umich.edu \
--to=rees@umich.edu \
--cc=bhalevy@tonian.com \
--cc=linux-nfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).