From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Coly Li <colyli@suse.de>
Cc: linux-raid@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
Neil Brown <neilb@suse.com>
Subject: Re: [PATCH] Fix regression during add devices
Date: Wed, 09 Mar 2016 13:30:49 -0500 [thread overview]
Message-ID: <wrfjio0v4i7a.fsf@redhat.com> (raw)
In-Reply-To: <1457500818-1586-1-git-send-email-colyli@suse.de> (Coly Li's message of "Wed, 9 Mar 2016 13:20:18 +0800")
Coly Li <colyli@suse.de> writes:
> From: Hannes Reinecke <hare@suse.de>
>
> Commit d180d2aa2a17 ("Manage: fix test for 'is array failed'.")
> introduced a regression which would not allow to re-add new
> drivers to a failed array.
>
> The patch is written by Hannes Reinecke, Neil Brown points out
> the buggy commit ID is d180d2aa2a17. Coly helps to submit the
> patch to mdadm upstream.
>
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> Cc: Coly Li <colyli@suse.de>
> Cc: Neil Brown <neilb@suse.com>
> ---
> Manage.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Coly,
Thanks for the fix - please use "Fixes: " to indicate which patch
introduced the bug, and the story of pushing the patch really belongs in
a comment below the --- line, so it doesn't go into git.
I modified it to look like this - please let me know if you are OK with
this.
Thanks,
Jes
commit 227bd322d3ed80bee0f1a0ae44a293908890851c
Author: Hannes Reinecke <hare@suse.de>
Date: Wed Mar 9 13:20:18 2016 +0800
Fix regression during add devices
Commit d180d2aa2a17 ("Manage: fix test for 'is array failed'.")
introduced a regression which would not allow to re-add new
drivers to a failed array.
Fixes: d180d2aa2a17 ("Manage: fix test for 'is array failed'.")
Signed-off-by: Hannes Reinecke <hare@suse.de>
Cc: Coly Li <colyli@suse.de>
Cc: Neil Brown <neilb@suse.com>
Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
> diff --git a/Manage.c b/Manage.c
> index 7e1b94b..073ddb9 100644
> --- a/Manage.c
> +++ b/Manage.c
> @@ -879,10 +879,10 @@ int Manage_add(int fd, int tfd, struct mddev_dev *dv,
> continue;
> if (disc.major == 0 && disc.minor == 0)
> continue;
> - found++;
> if (!(disc.state & (1<<MD_DISK_SYNC)))
> continue;
> avail[disc.raid_disk] = 1;
> + found++;
> }
> array_failed = !enough(array->level, array->raid_disks,
> array->layout, 1, avail);
next prev parent reply other threads:[~2016-03-09 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 5:20 [PATCH] Fix regression during add devices Coly Li
2016-03-09 18:30 ` Jes Sorensen [this message]
2016-03-10 4:59 ` Coly Li
2016-03-10 16:44 ` Jes Sorensen
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=wrfjio0v4i7a.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=colyli@suse.de \
--cc=hare@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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.