All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: NeilBrown <neilb@suse.de>
Cc: SandeepKsinha <sandeepksinha@gmail.com>,
	Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID0 - unitialised zone->dev_start for zone[0]
Date: Mon, 18 May 2009 10:45:20 -0400	[thread overview]
Message-ID: <4A117480.4030401@tmr.com> (raw)
In-Reply-To: <beb1238841d24e553e0248080d5e4dca.squirrel@neil.brown.name>

NeilBrown wrote:
> On Thu, May 14, 2009 3:08 am, SandeepKsinha wrote:
>   
>> Hi Neil,
>>
>>
>> [22:33:46 sinhas]$ diff raid0.c raid0.c.orig
>>     
>
> Always, always, always use "diff -u".  It provides context
> so the diff is much easier to read.
>
>   
>> 160d159
>> <       zone->dev_start = 0;
>> [/usr/src/linux-2.6.29/drivers/md]
>> [22:33:59 sinhas]$
>>
>> I see this piece of code missing and being used later.
>> Not very sure of the code flow, but still as part of defensive
>> programming.
>>
>> Am i missing something?
>>     
>
> conf->strip_zone is allocated with kzalloc, so all values are
> initialised to 0.
>   

To prevent future unnecessary analysis of this section, perhaps a 
comment instead of code would be appropriate?


-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc

"You are disgraced professional losers. And by the way, give us our money back."
    - Representative Earl Pomeroy,  Democrat of North Dakota
on the A.I.G. executives who were paid bonuses  after a federal bailout.



      parent reply	other threads:[~2009-05-18 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 17:08 RAID0 - unitialised zone->dev_start for zone[0] SandeepKsinha
2009-05-13 21:11 ` NeilBrown
2009-05-14  3:14   ` SandeepKsinha
2009-05-14  4:24     ` NeilBrown
2009-05-14  5:46       ` SandeepKsinha
2009-05-18 14:45   ` Bill Davidsen [this message]

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=4A117480.4030401@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=sandeepksinha@gmail.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 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.