From: Eryu Guan <eguan@redhat.com>
To: Jan Tulak <jtulak@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2] xfstests: Add mkfs input validation tests
Date: Wed, 29 Jun 2016 20:52:36 +0800 [thread overview]
Message-ID: <20160629125236.GM23649@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1467196693-9724-1-git-send-email-jtulak@redhat.com>
On Wed, Jun 29, 2016 at 12:38:13PM +0200, Jan Tulak wrote:
> mkfs.xfs does not do a very good job of input validation. This test
> is designed to exercise the input validation and test good/bad
> combinations of options being set. It will not pass on an old
> mkfs.xfs binary - it is designed to be the test case for an input
> validation cleanup (merged in spring/summer 2016).
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> Signed-off-by: Jan Tulak <jtulak@redhat.com>
>
> ---
>
> I didn't got other feedback than the three small issues fixed bellow, and it is
> passing on current xfsprogs-dev as it should. So I think that it can be merged.
Looks good to me.
>
> CHANGES:
> * Change copyright year to 2016
> * rm || true --> rm -f
> * Change from space to tab indent
>
> Cheers,
> Jan
>
> Signed-off-by: Jan Tulak <jtulak@redhat.com>
> ---
> tests/xfs/400-input-validation | 335 +++++++++++++++++++++++++++++++++++++
> tests/xfs/400-input-validation.out | 2 +
Only one problem with this test seq name. Current Makefile doesn't
support installing such test seq name
$(INSTALL) -m 755 [0-9]?? $(TARGET_DIR)
Can you please send another patch to fix this?
Thanks,
Eryu
next prev parent reply other threads:[~2016-06-29 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 8:31 [PATCH] xfstests: Add mkfs input validation tests Jan Tulak
2016-06-23 11:04 ` Eryu Guan
2016-06-23 11:10 ` Jan Tulak
2016-06-29 10:38 ` [PATCH v2] " Jan Tulak
2016-06-29 12:52 ` Eryu Guan [this message]
2016-06-29 13:03 ` Jan Tulak
2016-07-01 16:12 ` [PATCH v3] " Jan Tulak
2016-07-13 10:46 ` Eryu Guan
2016-07-14 10:20 ` Jan Tulak
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=20160629125236.GM23649@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=jtulak@redhat.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.