From: Dave Chinner <david@fromorbit.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 1/3] xfs: support realtime/log device setup changes in config sections
Date: Fri, 5 Feb 2016 08:04:55 +1100 [thread overview]
Message-ID: <20160204210455.GC31407@dastard> (raw)
In-Reply-To: <20160202043633.GD11419@eguan.usersys.redhat.com>
On Tue, Feb 02, 2016 at 12:36:33PM +0800, Eryu Guan wrote:
> On Thu, Jan 21, 2016 at 12:43:11PM +1100, Dave Chinner wrote:
> > From: Dave Chinner <dchinner@redhat.com>
> >
> > Currently changing the devices used by "USE_EXTERNAL" environmental
> > variable is not supported by the config section parsing. Add the
> > functionality so that we can use config sections to test external
> > device configs successfully.
> >
> > This required tracking down a bug in _check_xfs_filesystem() which
> > was causing a log device to be passed to a test device without an
> > external log device. This was caused by an uninitialised variable in
> > the function. I also added full output file removals to the first
> > couple of generic tests that were failing, because that's where the
> > check failure output ends up in this case.
> >
> > Signed-off-by: Dave Chinner <dchinner@redhat.com>
>
> Looks good to me. And I ran some tests on NFS/CIFS/XFS/overlay and the
> new _check_device function worked as expected. Just one white space
> issue below
>
> > ---
> > common/config | 63 +++++++++++++++++++++++++++++++++++++++----------------
> > common/dmflakey | 3 ++-
> > common/rc | 1 +
> > tests/generic/002 | 2 ++
> > tests/generic/004 | 2 ++
> > 5 files changed, 52 insertions(+), 19 deletions(-)
> >
> > diff --git a/common/config b/common/config
> > index cb34fd7..477753e 100644
> > --- a/common/config
> > +++ b/common/config
> > @@ -416,6 +416,30 @@ if [ -f "$HOST_OPTIONS" ]; then
> > fi
> > fi
> >
> > +_check_device()
> > +{
> > + local name=$1
> > + local dev_needed=$2
> > + local dev=$3
> > +
> > + if [ -z "$dev" ]; then
> > + if [ "$dev_needed" == "required" ]; then
>
> Above line introduced trailing white space.
Fixed, so can I add your reviewed-by?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-02-04 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 1:43 [PATCH 0/3] fstests: improved config section support Dave Chinner
2016-01-21 1:43 ` [PATCH 1/3] xfs: support realtime/log device setup changes in config sections Dave Chinner
2016-02-02 4:36 ` Eryu Guan
2016-02-04 21:04 ` Dave Chinner [this message]
2016-02-05 2:46 ` Eryu Guan
2016-01-21 1:43 ` [PATCH 2/3] setup: add section support Dave Chinner
2016-02-05 3:33 ` Eryu Guan
2016-01-21 1:43 ` [PATCH 3/3] check: add exclude sections CLI parameter Dave Chinner
2016-02-02 3:34 ` [PATCH 0/3] fstests: improved config section support Dave Chinner
2016-02-04 21:06 ` Dave Chinner
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=20160204210455.GC31407@dastard \
--to=david@fromorbit.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
/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