From: NeilBrown <neilb@suse.de>
To: mwilck@arcor.de
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 00/10] Two bug fixes and a lot of debug code
Date: Wed, 31 Jul 2013 13:10:27 +1000 [thread overview]
Message-ID: <20130731131027.73a0ec0f@notabene.brown> (raw)
In-Reply-To: <1375219114-5626-1-git-send-email-mwilck@arcor.de>
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
On Tue, 30 Jul 2013 23:18:24 +0200 mwilck@arcor.de wrote:
> From: Martin Wilck <mwilck@arcor.de>
>
> This patch series fixes the "suspicious test failure" mentioned
> in an earlier posting to linux-raid, and another bug introduced
> by myself. Besides, it contains a lot of DEBUG code that was
> necessary to understand the "suspicious" problem.
>
> Verified that the 09 and 10 unit test series are not broken.
>
> Martin Wilck (10):
> DDF: ddf_activate_spare: bugfix for 62ff3c40
> DDF: log disk status changes more nicely
> DDF: ddf_process_update: log offsets for conf changes
> DDF: load_ddf_header: more error logging
> DDF: ddf_set_disk: add some debug messages
> monitor: read_and_act: log status when called
> mdmon: wait_and_act: fix debug message for SIGUSR1
> mdmon: manage_member: debug messages for array state
> mdmon: manage_member: fix race condition during slow meta data writes
> tests/10ddf-create-fail-rebuild: new unit test for DDF
>
> managemon.c | 11 +++++-
> monitor.c | 25 +++++++++++--
> super-ddf.c | 75 +++++++++++++++++++++++++++++---------
> tests/10ddf-create-fail-rebuild | 77 +++++++++++++++++++++++++++++++++++++++
> 4 files changed, 166 insertions(+), 22 deletions(-)
> create mode 100644 tests/10ddf-create-fail-rebuild
Thanks. All applied with one small change as already mentioned.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-07-31 3:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 20:58 Suspicious test failure - mdmon misses recovery events on loop devices Martin Wilck
2013-07-29 6:55 ` NeilBrown
2013-07-29 20:39 ` Martin Wilck
2013-07-29 20:42 ` Martin Wilck
2013-07-30 0:42 ` NeilBrown
2013-07-30 21:16 ` Martin Wilck
2013-07-30 21:18 ` [PATCH 00/10] Two bug fixes and a lot of debug code mwilck
2013-07-31 3:10 ` NeilBrown [this message]
2013-07-30 21:18 ` [PATCH 01/10] DDF: ddf_activate_spare: bugfix for 62ff3c40 mwilck
2013-07-30 21:18 ` [PATCH 02/10] DDF: log disk status changes more nicely mwilck
2013-07-30 21:18 ` [PATCH 03/10] DDF: ddf_process_update: log offsets for conf changes mwilck
2013-07-30 21:18 ` [PATCH 04/10] DDF: load_ddf_header: more error logging mwilck
2013-07-30 21:18 ` [PATCH 05/10] DDF: ddf_set_disk: add some debug messages mwilck
2013-07-30 21:18 ` [PATCH 06/10] monitor: read_and_act: log status when called mwilck
2013-07-31 2:59 ` NeilBrown
2013-07-31 5:28 ` Martin Wilck
2013-07-30 21:18 ` [PATCH 07/10] mdmon: wait_and_act: fix debug message for SIGUSR1 mwilck
2013-07-30 21:18 ` [PATCH 08/10] mdmon: manage_member: debug messages for array state mwilck
2013-07-30 21:18 ` [PATCH 09/10] mdmon: manage_member: fix race condition during slow meta data writes mwilck
2013-07-30 21:18 ` [PATCH 10/10] tests/10ddf-create-fail-rebuild: new unit test for DDF mwilck
2013-07-31 5:36 ` [PATCH] tests/env-ddf-template: helper for new unit test mwilck
2013-07-31 6:49 ` 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=20130731131027.73a0ec0f@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mwilck@arcor.de \
/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).