From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>, Balbir Singh <balbir@in.ibm.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH -tip] Documentation/accounting/getdelays.c intialize the variable before using it
Date: Wed, 27 May 2009 12:33:26 +0530 [thread overview]
Message-ID: <1243407806.12592.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20090526235442.d793ac89.akpm@linux-foundation.org>
On Tue, 2009-05-26 at 23:54 -0700, Andrew Morton wrote:
> On Wed, 20 May 2009 10:44:44 +0530 Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
>
> >
> > May be in some cases cmd_type will be used uninitialized.
> >
> > Also fixes compilation warning:
> >
> > CC [M] Documentation/DocBook/procfs_example.o
> > Documentation/accounting/getdelays.c: In function ___main___:
> > Documentation/accounting/getdelays.c:249: warning: ___cmd_type___ may be used uninitialized in this function
> >
> > Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> > ---
> > Documentation/accounting/getdelays.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/Documentation/accounting/getdelays.c b/Documentation/accounting/getdelays.c
> > index 7ea2311..36aae3b 100644
> > --- a/Documentation/accounting/getdelays.c
> > +++ b/Documentation/accounting/getdelays.c
> > @@ -246,7 +246,7 @@ void print_ioacct(struct taskstats *t)
> >
> > int main(int argc, char *argv[])
> > {
> > - int c, rc, rep_len, aggr_len, len2, cmd_type;
> > + int c, rc, rep_len, aggr_len, len2, cmd_type = TASKSTATS_CMD_ATTR_UNSPEC;
> > __u16 id;
> > __u32 mypid;
> >
>
> >From my reading of the code there is no bug here - we'll only use
> cmd_type if tid != 0, and cmd_type is always initialised when tid != 0.
>
> But I suppose we should squish the warning anyway.
>
> btw, whichever version of gcc you're using has apparently regressed -
> my gcc-4.3.0 manages to work out what's happening. Hence please prefer
> to include the gcc version in the changelog. And send a bug report at
> the gcc guys if appropriate ;)
my gcc version is 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC)
But I heard from jejb that 4.3.3 fixed some of these warnings.
Thanks,
--
JSR
next prev parent reply other threads:[~2009-05-27 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 5:14 [PATCH -tip] Documentation/accounting/getdelays.c intialize the variable before using it Jaswinder Singh Rajput
2009-05-27 6:54 ` Andrew Morton
2009-05-27 7:03 ` Jaswinder Singh Rajput [this message]
2009-05-27 12:17 ` Balbir Singh
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=1243407806.12592.3.camel@localhost.localdomain \
--to=jaswinder@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=x86@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