linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Jes.Sorensen@redhat.com
Cc: linux-raid@vger.kernel.org, gqjiang@suse.com,
	Zhilong Liu <zlliu@suse.com>
Subject: Re: [PATCH RFC] test: revise 'test' and make it easier to understand
Date: Fri, 03 Mar 2017 09:26:43 +1100	[thread overview]
Message-ID: <87mvd3nwm4.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <1488250053-10436-1-git-send-email-zlliu@suse.com>

[-- Attachment #1: Type: text/plain, Size: 1674 bytes --]

On Tue, Feb 28 2017, Zhilong Liu wrote:

> 1. use 'Tab' as the code style.
> 2. arrange the testing steps and provide the 'main' entrance.
> 3. draft the log_save feature, it captures the /proc/mdstat,
>    md superblock info, bitmap info and the detail dmesg.
> 4. modified the mdadm() func, adding the operation that clear
>    the superblock when create or build one new array, and it
>    would exit testing when mdadm command returned non-0 value.
> 5. delete no_errors() func, it only used in tests/04update-uuid,
>    I recommend the new mdadm() using method.
> 6. delete fast_sync() func.
> 7. testdev(), add the object file checking, otherwise this command
>    would create one regular file, it's one trouble thing.
> 8. add dmesg checking in do_test() func, it's necessary to check
>    dmesg whether or not printed abnormal message.
> 9. add checking conditions in main(), such as $pwd/raid6check need
>    exists, here is a prompt to remind users to 'make everything'
>    before testing; the $targetdir should mount under ext[2-4] FS,
>    because the external bitmap only supports ext, the bmap() API
>    of bitmap.c doesn't exist in all filesystem, such as btrfs.
>
> Signed-off-by: Zhilong Liu <zlliu@suse.com>

I haven't looked at this patch in any great detail, but I just wanted to
say I think it is great that 'test' is getting some attention like this.
I sort of just grew over the years without any clear plan.  It probably
has all sorts of strange things in it that don't make a lot of sense any
more.
So I've very happy for you to rip it apart and put it together is a more
coherent form.  Thanks!

Acked-by: NeilBrown <neilb@suse.com>

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-03-02 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 12:37 exposed and pushed the mdadm/test improvement progress zhilong
2017-02-28  2:47 ` [PATCH RFC] test: revise 'test' and make it easier to understand Zhilong Liu
2017-03-02 22:26   ` NeilBrown [this message]
2017-03-03  8:06   ` Guoqing Jiang
2017-03-06  3:27     ` zhilong

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=87mvd3nwm4.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=Jes.Sorensen@redhat.com \
    --cc=gqjiang@suse.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=zlliu@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 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).