From: Eryu Guan <guaneryu@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>, xuyang.jy@cn.fujitsu.com
Cc: david@fromorbit.com, fstests@vger.kernel.org
Subject: Re: [PATCH v3] common/xfs: Add require_xfs_db_write_array function
Date: Wed, 18 Apr 2018 12:29:38 +0800 [thread overview]
Message-ID: <20180418042938.GM2932@desktop> (raw)
In-Reply-To: <20180417175917.GD5201@magnolia>
On Tue, Apr 17, 2018 at 10:59:17AM -0700, Darrick J. Wong wrote:
> On Tue, Apr 17, 2018 at 02:11:40PM +0800, yang xu wrote:
> > xfsprogs commit 4222d00("db: write via array indexing doesn't
> > work") fixes a bug that xfs_db write can't support array indexing.
> > This function will check whether the bug is fixed on the current
> > xfsprogs.
> >
> > xfs/444 applies the function, and skips if this bug exists.
> >
> > Signed-off-by: yang xu <xuyang.jy@cn.fujitsu.com>
> > ---
> > common/xfs | 17 +++++++++++++++++
> > tests/xfs/444 | 1 +
> > 2 files changed, 18 insertions(+)
> >
> > diff --git a/common/xfs b/common/xfs
> > index 3169f87..0b59994 100644
> > --- a/common/xfs
> > +++ b/common/xfs
> > @@ -701,3 +701,20 @@ _scratch_xfs_set_sb_field()
> > {
> > _scratch_xfs_set_metadata_field "$1" "$2" "sb 0"
> > }
> > +
> > +#Before xfsprogs commit 4222d000ed("db: write via array indexing doesn't work"),
> > +##xfs_db command to write a specific AGFL index doesn't work.
I'll add more comments here to explain why we require a bug fix instead
of exposing the bug to users, e.g.
"It's a bug in a diagnostic tool that is only used by XFS developers as
a test infrastructure, so we can treat it as a infrastructure dependency
as all other _require rules."
> > +_require_xfs_db_write_array()
> > +{
> > + local supported=0
> > +
> > + _require_test
> > + touch $TEST_DIR/$seq.img
> > + $MKFS_XFS_PROG -d file,name=$TEST_DIR/$seq.img,size=512m >/dev/null 2>&1
> > + $XFS_DB_PROG -x -c "agfl 0" -c "write bno[32] 78" $TEST_DIR/$seq.img \
> > + >/dev/null 2>&1
> > + $XFS_DB_PROG -x -c "agfl 0" -c "print bno[32]" $TEST_DIR/$seq.img \
> > + | grep -q "bno\[32\] = 78" && supported=1
> > + rm -f $TEST_DIR/$seq.img
> > + [ $supported -eq 0 ] && _notrun "xfs_db write can't support array"
> > +}
> > diff --git a/tests/xfs/444 b/tests/xfs/444
> > index 141be52..9700422 100755
> > --- a/tests/xfs/444
> > +++ b/tests/xfs/444
> > @@ -54,6 +54,7 @@ _supported_os Linux
> > _require_check_dmesg
> > _require_scratch
> > _require_test_program "punch-alternating"
> > +_require_xfs_db_write_array
>
> Looks ok,
> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Thanks for the review!
Eryu
>
> --D
>
> >
> > # This is only a v5 filesystem problem
> > _require_scratch_xfs_crc
> > --
> > 1.8.3.1
> >
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe fstests" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-04-18 4:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 10:00 [PATCH] xfs/444: add check for xfs_db write bno array yang xu
2018-04-12 12:09 ` Dave Chinner
2018-04-12 13:00 ` Eryu Guan
2018-04-12 23:00 ` Dave Chinner
2018-04-13 4:36 ` Eryu Guan
2018-04-13 13:42 ` Dave Chinner
2018-04-16 6:00 ` Eryu Guan
2018-04-16 9:07 ` [PATCH v2] common/xfs: Add require_xfs_db_write_array function yang xu
2018-04-16 17:22 ` Darrick J. Wong
[not found] ` <5AD5721C.10709@cn.fujitsu.com>
2018-04-17 4:06 ` Darrick J. Wong
2018-04-17 6:11 ` [PATCH v3] " yang xu
2018-04-17 17:59 ` Darrick J. Wong
2018-04-18 4:29 ` Eryu Guan [this message]
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=20180418042938.GM2932@desktop \
--to=guaneryu@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=xuyang.jy@cn.fujitsu.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