From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: [PATCH 001 of 4] md: Fix bug where spares don't always get rebuilt properly when they become live.
Date: Mon, 23 Oct 2006 17:07:48 +1000 [thread overview]
Message-ID: <1061023070748.29223@suse.de> (raw)
In-Reply-To: 20061023170347.29132.patches@notabene
If save_raid_disk is >= 0, then the device could be a device that is
already in sync that is being re-added. So we need to default this
value to -1.
Signed-off-by: Neil Brown <neilb@suse.de>
### Diffstat output
./drivers/md/md.c | 1 +
1 file changed, 1 insertion(+)
diff .prev/drivers/md/md.c ./drivers/md/md.c
--- .prev/drivers/md/md.c 2006-10-23 16:34:55.000000000 +1000
+++ ./drivers/md/md.c 2006-10-23 16:35:05.000000000 +1000
@@ -2003,6 +2003,7 @@ static mdk_rdev_t *md_import_device(dev_
kobject_init(&rdev->kobj);
rdev->desc_nr = -1;
+ rdev->saved_raid_disk = -1;
rdev->flags = 0;
rdev->data_offset = 0;
rdev->sb_events = 0;
WARNING: multiple messages have this Message-ID (diff)
From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: stable@kernel.org
Subject: [PATCH 001 of 4] md: Fix bug where spares don't always get rebuilt properly when they become live.
Date: Mon, 23 Oct 2006 17:07:48 +1000 [thread overview]
Message-ID: <1061023070748.29223@suse.de> (raw)
In-Reply-To: 20061023170347.29132.patches@notabene
If save_raid_disk is >= 0, then the device could be a device that is
already in sync that is being re-added. So we need to default this
value to -1.
Signed-off-by: Neil Brown <neilb@suse.de>
### Diffstat output
./drivers/md/md.c | 1 +
1 file changed, 1 insertion(+)
diff .prev/drivers/md/md.c ./drivers/md/md.c
--- .prev/drivers/md/md.c 2006-10-23 16:34:55.000000000 +1000
+++ ./drivers/md/md.c 2006-10-23 16:35:05.000000000 +1000
@@ -2003,6 +2003,7 @@ static mdk_rdev_t *md_import_device(dev_
kobject_init(&rdev->kobj);
rdev->desc_nr = -1;
+ rdev->saved_raid_disk = -1;
rdev->flags = 0;
rdev->data_offset = 0;
rdev->sb_events = 0;
next prev parent reply other threads:[~2006-10-23 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 7:07 [PATCH 000 of 4] md: assorted bugfixes - one serious NeilBrown
2006-10-23 7:07 ` NeilBrown
2006-10-23 7:07 ` NeilBrown [this message]
2006-10-23 7:07 ` [PATCH 001 of 4] md: Fix bug where spares don't always get rebuilt properly when they become live NeilBrown
2006-10-23 7:07 ` [PATCH 002 of 4] md: Simplify checking of available size when resizing an array NeilBrown
2006-10-23 7:08 ` [PATCH 003 of 4] md: Fix up maintenance of ->degraded in multipath NeilBrown
2006-10-23 7:08 ` [PATCH 004 of 4] md: Fix printk format warnings, seen on powerpc64: NeilBrown
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=1061023070748.29223@suse.de \
--to=neilb@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=stable@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 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.