From: Dave Chinner <david@fromorbit.com>
To: yang xu <xuyang.jy@cn.fujitsu.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs/444: add check for xfs_db write bno array
Date: Thu, 12 Apr 2018 22:09:52 +1000 [thread overview]
Message-ID: <20180412120952.GM729@dastard> (raw)
In-Reply-To: <1523527230-6394-1-git-send-email-xuyang.jy@cn.fujitsu.com>
On Thu, Apr 12, 2018 at 06:00:30PM +0800, yang xu wrote:
> On RHEL7.5Alpha, the test case can trigger an xfsprogs bug that xfs_db
> writes bno array failed ,such as:
> $ xfs_db -x -c "agfl 0" -c "write bno[32] 78" /dev/sda9
> bno[32] = 32:null 33:null 34:null 35:null 36:null 37:null ...
>
> the correct result as below:
> bno[32] = 78
>
> On xfs/444 the following code triggers this bug:
> cat $tmp.remap | while read dest_pos bno junk; do
> _scratch_xfs_set_metadata_field "bno[$dest_pos]" "$bno" \
> "agfl 0" >> $seqres.full
> done
>
> It is because xfs_db on RHEL7.5Alpha doesn't support write via array
> indexing. The problem has been fixed since xfprogs commit 4222d000ed
> ("db: write via array indexing doesn't work"). But the fix patch has
> not been merged into RHEL7.5Alpha.
>
> For users, they should know the reason for the failure of the test is
> a filesystem bug or an xfsprogs bug. So, we add check for xfs_db
> write bno array.
>
> Signed-off-by: yang xu <xuyang.jy@cn.fujitsu.com>
> ---
> tests/xfs/444 | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/tests/xfs/444 b/tests/xfs/444
> index 141be52..fe80502 100755
> --- a/tests/xfs/444
> +++ b/tests/xfs/444
> @@ -58,6 +58,22 @@ _require_test_program "punch-alternating"
> # This is only a v5 filesystem problem
> _require_scratch_xfs_crc
>
> +check_xfs_db_write_bno_array() {
_require_xfs_db_write_array(), and move to common/xfs.
> + _scratch_xfs_set_metadata_field "bno[32]" "78" "agfl 0" >> $seqres.full
> +
> + # Before xfsprogs commit 0ebbf1d58898 ("db: limit AGFL bno
> + # arrayi printing), When asking for a single agfl entry,
> + # the result outputs the entire remainder of the array
> + # starting at the given index.
> + # It is difficult to extract single entry values.
> + # So filter them.
> + bno2=$(_scratch_xfs_get_metadata_field "bno[32]" \
> + "agfl 0" |sed -e 's/ .*$//g' | sed -e 's/^.*://g')
> + echo "bno[32] set 78 get $bno2" >> $seqres.full
> +
> + [ "${bno2}" != "78" ] && _fail "xfs_db write can't support bno array"
test should _notrun is db doesn't have therequired support, not
_fail.
> +#Before xfsprogs commit 4222d000ed("db: write via array indexing doesn't work").
> +#xfs_db command to write a specific AGFL index doesn't work. We should check it.
> +check_xfs_db_write_bno_array
This comment belongs with the function, not the caller.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-04-12 12:09 UTC|newest]
Thread overview: 14+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2018-04-16 6:27 [PATCH] xfs/444: add check for xfs_db write bno array Xu, Yang
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=20180412120952.GM729@dastard \
--to=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