From: Neil Brown <neilb@suse.de>
To: Krzysztof Wojcik <krzysztof.wojcik@intel.com>
Cc: linux-raid@vger.kernel.org, wojciech.neubauer@intel.com,
adam.kwolek@intel.com, dan.j.williams@intel.com,
ed.ciechanowski@intel.com
Subject: Re: [PATCH 6/6] FIX: Unblock disk in kernel only if it is blocked.
Date: Wed, 26 Jan 2011 11:06:26 +1000 [thread overview]
Message-ID: <20110126110626.2d280ef0@nbeee.brown> (raw)
In-Reply-To: <20110119162349.8738.43217.stgit@gklab-128-111.igk.intel.com>
On Wed, 19 Jan 2011 17:23:49 +0100
Krzysztof Wojcik <krzysztof.wojcik@intel.com> wrote:
> Missing condition during setting next state for disk.
Yet again you completely fail to explain why you want to make this
change.
And again it looks wrong.
There is no harm is setting "-blocked" if the device is not actually
blocked is there?
PLEASE PLEASE PLEASE explain exactly the problem you are trying to
fix. Don't waste my time and yours by making have to continually ask
for explanations.
NeilBrown
>
> Signed-off-by: Krzysztof Wojcik <krzysztof.wojcik@intel.com>
> ---
> monitor.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/monitor.c b/monitor.c
> index ed3ce49..4fba5fd 100644
> --- a/monitor.c
> +++ b/monitor.c
> @@ -336,7 +336,9 @@ static int read_and_act(struct active_array *a)
> a->container->ss->set_disk(a,
> mdi->disk.raid_disk, mdi->curr_state);
> check_degraded = 1;
> - mdi->next_state |= DS_UNBLOCK;
> + /* if '-blocked' wasn't passed to kernel, do
> it now */
> + if (mdi->curr_state == DS_BLOCKED)
> + mdi->next_state |= DS_UNBLOCK;
> if (a->curr_state == read_auto) {
> a->container->ss->set_array_state(a,
> 0); a->next_state = active;
next prev parent reply other threads:[~2011-01-26 1:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 16:23 [PATCH 0/6] A few fixes connected with raid0<->raid10 takeover Krzysztof Wojcik
2011-01-19 16:23 ` [PATCH 1/6] Limit no-restriping operations only for raid5 Krzysztof Wojcik
2011-01-26 1:01 ` Neil Brown
2011-01-26 11:56 ` Wojcik, Krzysztof
2011-01-19 16:23 ` [PATCH 2/6] FIX: Ping manager after level change Krzysztof Wojcik
2011-01-19 16:23 ` [PATCH 3/6] Check number of failed disks durig raid10->raid0 takeover Krzysztof Wojcik
2011-01-19 16:23 ` [PATCH 4/6] FIX: Remove disks in mdmon for external metadata Krzysztof Wojcik
2011-01-26 1:04 ` Neil Brown
2011-01-26 13:00 ` Wojcik, Krzysztof
2011-01-19 16:23 ` [PATCH 5/6] FIX: Reset disk state if disk is missing Krzysztof Wojcik
2011-01-19 16:23 ` [PATCH 6/6] FIX: Unblock disk in kernel only if it is blocked Krzysztof Wojcik
2011-01-26 1:06 ` Neil Brown [this message]
2011-01-26 14:22 ` Wojcik, Krzysztof
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=20110126110626.2d280ef0@nbeee.brown \
--to=neilb@suse.de \
--cc=adam.kwolek@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=krzysztof.wojcik@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=wojciech.neubauer@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox