public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Srihari Vijayaraghavan <harisri@bigpond.com>,
	Andrea Arcangeli <andrea@suse.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Solved 2.4.21-pre3aa1 and RAID-0 issue (was: Re: 2.4.21-pre3aa1 and RAID0 issue]
Date: Mon, 27 Jan 2003 12:30:02 +0100	[thread overview]
Message-ID: <20030127113002.GB889@suse.de> (raw)
In-Reply-To: <200301271441.11112.harisri@bigpond.com>

On Mon, Jan 27 2003, Srihari Vijayaraghavan wrote:
> Hello Andrea,
> 
> On Thursday 23 January 2003 01:02, Srihari Vijayaraghavan wrote:
> > ...
> > Ok. I did some more testing, and this is what happens:
> > /sbin/raidstart /dev/md0 executes and exits fine under 2.4.21-pre3. Where
> > as under 2.4.21-pre3aa1 it starts executing but _never_ exits (I waited for
> > few minutes). I had to kill it using alt + sysrq + k.
> > ...
> 
> The 9985_blk-atomic-aa5 patch is causing this regression. Backing this patch 
> out of 2.4.21-pre3aa1 makes it to work nicely with Software RAID-0.

Could you please try this patch on top of 2.4.21-pre3aa1 instead of
backing out blk-atomic? Does that work, too? Thanks!

===== drivers/md/md.c 1.38 vs edited =====
--- 1.38/drivers/md/md.c	Thu Jan 16 00:15:01 2003
+++ edited/drivers/md/md.c	Mon Jan 27 12:23:41 2003
@@ -494,6 +494,7 @@
 	bh.b_page = page;
 	bh.b_reqnext = NULL;
 	bh.b_data = page_address(page);
+	bh.b_elv_sequence = 0;
 	generic_make_request(rw, &bh);
 
 	run_task_queue(&tq_disk);
===== drivers/md/raid1.c 1.15 vs edited =====
--- 1.15/drivers/md/raid1.c	Sat Aug 31 02:20:48 2002
+++ edited/drivers/md/raid1.c	Mon Jan 27 12:27:44 2003
@@ -686,6 +686,7 @@
  		mbh->b_list       = BUF_LOCKED;
  		mbh->b_end_io     = raid1_end_request;
  		mbh->b_private    = r1_bh;
+		mbh->b_elv_sequence = bh->b_elv_sequence;
 
 		mbh->b_next = r1_bh->mirror_bh_list;
 		r1_bh->mirror_bh_list = mbh;
@@ -1456,6 +1457,7 @@
 	bh->b_private = r1_bh;
 	bh->b_blocknr = sector_nr;
 	bh->b_rsector = sector_nr;
+	bh->b_elv_sequence = 0;
 	init_waitqueue_head(&bh->b_wait);
 
 	generic_make_request(READ, bh);

-- 
Jens Axboe


  reply	other threads:[~2003-01-27 11:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-26 21:56 2.4.21-pre2aa1 - RAID0 issue Srihari Vijayaraghavan
2003-01-22  9:07 ` 2.4.21-pre3aa1 and RAID0 issue (was: 2.4.21-pre2aa1 - RAID0 issue.) Srihari Vijayaraghavan
2003-01-22 14:02   ` Srihari Vijayaraghavan
2003-01-27  3:41     ` Solved 2.4.21-pre3aa1 and RAID-0 issue (was: Re: 2.4.21-pre3aa1 and RAID0 issue] Srihari Vijayaraghavan
2003-01-27 11:30       ` Jens Axboe [this message]
2003-01-28  9:46         ` Srihari Vijayaraghavan
2003-01-28  9:44           ` Jens Axboe
2003-01-28 12:24             ` Andrea Arcangeli

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=20030127113002.GB889@suse.de \
    --to=axboe@suse.de \
    --cc=andrea@suse.de \
    --cc=harisri@bigpond.com \
    --cc=linux-kernel@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