linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Paul Menzel <pm.debian@googlemail.com>
Cc: Tim Gardner <tim.gardner@canonical.com>,
	linux-kernel@vger.kernel.org, Alasdair Kergon <agk@redhat.com>,
	dm-devel@redhat.com, linux-raid@vger.kernel.org
Subject: Re: [PATCH linux-next] DM RAID: validate_raid_redundancy: Silence uninitialized variable warning
Date: Thu, 21 Feb 2013 09:37:44 +1100	[thread overview]
Message-ID: <20130221093744.3ad146c4@notabene.brown> (raw)
In-Reply-To: <1361398597.4895.24.camel@mattotaupa>

[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]

On Wed, 20 Feb 2013 23:16:37 +0100 Paul Menzel <pm.debian@googlemail.com>
wrote:

> Dear Tim,
> 
> 
> thanks for the patch.
> 
> 
> Am Mittwoch, den 20.02.2013, 13:31 -0700 schrieb Tim Gardner:
> 
> Noting the `gcc` version and build environment is never wrong. ;-)
> 
> > drivers/md/dm-raid.c: In function 'raid_ctr':
> > drivers/md/dm-raid.c:453:53: warning: 'rebuilds_per_group' may be used uninitialized in this function [-Wuninitialized]
> > drivers/md/dm-raid.c:383:11: note: 'rebuilds_per_group' was declared here
> > 
> > It appears unlikely that rebuilds_per_group could be used before set,
> 
> Why? Otherwise the compiler would not complain, right?

It is not simply unlikely, it is impossible.  But gcc isn't that clever yet.

> > --- a/drivers/md/dm-raid.c
> > +++ b/drivers/md/dm-raid.c
> > @@ -380,7 +380,7 @@ static int validate_region_size(struct raid_set *rs, unsigned long region_size)
> >  static int validate_raid_redundancy(struct raid_set *rs)
> >  {
> >  	unsigned i, rebuild_cnt = 0;
> > -	unsigned rebuilds_per_group, copies, d;
> > +	unsigned rebuilds_per_group = 0, copies, d;

This should either be:
        unsigned uninitialized_var(rebuilds_per_group);
        unsigned copies, d;

which the old way and is being deprecated, but at least is consistent with
the kernel as it is, or

        unsigned rebuilds_per_group = 0 /* GCC */;
	unsigned copies,d;

which is apparently the new way which I believe is due to be imposed on the
kernel immediately after 3.9-rc1
   https://lwn.net/Articles/529954/

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2013-02-20 22:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 20:31 [PATCH linux-next] DM RAID: validate_raid_redundancy: Silence uninitialized variable warning Tim Gardner
2013-02-20 22:16 ` Paul Menzel
2013-02-20 22:18   ` Paul Menzel
2013-02-20 22:37   ` NeilBrown [this message]
2013-02-21 13:19 ` [dm-devel] " Alasdair G Kergon
2013-02-21 14:50   ` [PATCH linux-next v2] " Tim Gardner
2013-06-13 15:30     ` Tommi Rantala
2013-06-13 16:00       ` Tim Gardner

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=20130221093744.3ad146c4@notabene.brown \
    --to=neilb@suse.de \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=pm.debian@googlemail.com \
    --cc=tim.gardner@canonical.com \
    /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).