linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Jeff Zheng <Jeff.Zheng@endace.com>
Cc: david@lang.hm,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	Ingo Molnar <mingo@elte.hu>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: RE: Software raid0 will crash the file-system, when each disk is 5TB
Date: Fri, 18 May 2007 10:21:53 +1000	[thread overview]
Message-ID: <17996.61857.486525.172950@notabene.brown> (raw)
In-Reply-To: message from Jeff Zheng on Friday May 18

On Friday May 18, Jeff.Zheng@endace.com wrote:
>  Fix confirmed, filled the whole 11T hard disk, without crashing.
> I presume this would go into 2.6.22

Yes, and probably 2.6.21.y, though the patch will be slightly
different, see below.
> 
> Thanks again.

And thank-you for pursuing this with me.

NeilBrown


---------------------------
Avoid overflow in raid0 calculation with large components.

If a raid0 has a component device larger than 4TB, and is accessed on
a 32bit machines, then as 'chunk' is unsigned lock,
   chunk << chunksize_bits
can overflow (this can be as high as the size of the device in KB).
chunk itself will not overflow (without triggering a BUG).

So change 'chunk' to be 'sector_t, and get rid of the 'BUG' as it becomes
impossible to hit.

Cc: "Jeff Zheng" <Jeff.Zheng@endace.com>
Signed-off-by: Neil Brown <neilb@suse.de>

### Diffstat output
 ./drivers/md/raid0.c |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff .prev/drivers/md/raid0.c ./drivers/md/raid0.c
--- .prev/drivers/md/raid0.c	2007-05-17 10:33:30.000000000 +1000
+++ ./drivers/md/raid0.c	2007-05-17 16:14:12.000000000 +1000
@@ -415,7 +415,7 @@ static int raid0_make_request (request_q
 	raid0_conf_t *conf = mddev_to_conf(mddev);
 	struct strip_zone *zone;
 	mdk_rdev_t *tmp_dev;
-	unsigned long chunk;
+	sector_t chunk;
 	sector_t block, rsect;
 	const int rw = bio_data_dir(bio);
 
@@ -470,7 +470,6 @@ static int raid0_make_request (request_q
 
 		sector_div(x, zone->nb_dev);
 		chunk = x;
-		BUG_ON(x != (sector_t)chunk);
 
 		x = block >> chunksize_bits;
 		tmp_dev = zone->dev[sector_div(x, zone->nb_dev)];

  reply	other threads:[~2007-05-18  0:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <659F626D666070439A4A5965CD6EBF406836C6@gazelle.ad.endace.com>
2007-05-15 23:29 ` Software raid0 will crash the file-system, when each disk is 5TB Michal Piotrowski
2007-05-16  0:03   ` Neil Brown
2007-05-16  1:56     ` Jeff Zheng
2007-05-16 17:28       ` Bill Davidsen
2007-05-16 17:58         ` david
2007-05-17  0:48       ` Neil Brown
2007-05-17  2:09         ` Jeff Zheng
2007-05-17  2:45           ` Neil Brown
2007-05-17  3:11             ` Jeff Zheng
2007-05-17  4:32               ` Neil Brown
2007-05-17  5:08                 ` Jeff Zheng
2007-05-17  4:45             ` david
2007-05-17  5:03               ` Neil Brown
2007-05-17  5:31                 ` Neil Brown
2007-05-17  5:38                   ` Jeff Zheng
2007-05-17 22:55                     ` Jeff Zheng
2007-05-18  0:21                       ` Neil Brown [this message]
2007-05-22 21:31                       ` Bill Davidsen

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=17996.61857.486525.172950@notabene.brown \
    --to=neilb@suse.de \
    --cc=Jeff.Zheng@endace.com \
    --cc=david@lang.hm \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=mingo@elte.hu \
    /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).