From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xiao yang <yangx.jy@cn.fujitsu.com>
Cc: fstests@vger.kernel.org, eguan@redhat.com
Subject: Re: [PATCH v2 1/2] common/xfs: Check if write supports [-c|-d] option in xfs_db
Date: Fri, 12 Jan 2018 08:43:27 -0800 [thread overview]
Message-ID: <20180112164327.GG5606@magnolia> (raw)
In-Reply-To: <1515737783-2061-1-git-send-email-yangx.jy@cn.fujitsu.com>
On Fri, Jan 12, 2018 at 02:16:22PM +0800, xiao yang wrote:
> Make sure _scratch_xfs_set_metadata_field() can be used on an
> old xfsprogs-dev(e.g. v3.1.1).
>
> The "-d" option was introduced since xfsprogs-dev v4.7.0 by commit
> 86769b3 ("xfs_db: allow recalculating CRCs on invalid metadata").
>
> The special argument "--" is only used to end option-scanning
> in getopt(). getopt() was introduced since xfsprogs-dev v3.2.3 by
> commit c9f5e3d ("xfs_db: Allow writes of corrupted data")'.
>
> Signed-off-by: xiao yang <yangx.jy@cn.fujitsu.com>
> ---
> common/xfs | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/common/xfs b/common/xfs
> index 45b84a0..59d6dd3 100644
> --- a/common/xfs
> +++ b/common/xfs
> @@ -658,8 +658,11 @@ _scratch_xfs_set_metadata_field()
> for arg in "$@"; do
> cmds+=("-c" "${arg}")
> done
> - _scratch_xfs_db -x "${cmds[@]}" -c "write -d ${key} -- ${value}"
> - echo
> +
> + local wr_cmd="write"
> + _scratch_xfs_db -x -c "help write" | egrep -q "(-c|-d)" && value="-- $value"
"${value}" at the end of this line, for consistency within the function?
Looks ok,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
> + _scratch_xfs_db -x -c "help write" | egrep -q "(-d)" && wr_cmd="${wr_cmd} -d"
> + _scratch_xfs_db -x "${cmds[@]}" -c "${wr_cmd} ${key} ${value}"
> }
>
> _scratch_xfs_get_sb_field()
> --
> 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-01-12 16:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 8:25 [PATCH] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-11 18:07 ` Darrick J. Wong
2018-01-12 1:58 ` Xiao Yang
2018-01-12 6:14 ` [PATCH v2] syscalls/madvise09.c: Use custom mount point instead of /sys/fs/cgroup/memory xiao yang
2018-01-12 6:14 ` [PATCH v2] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-12 6:19 ` [PATCH v2] syscalls/madvise09.c: Use custom mount point instead of /sys/fs/cgroup/memory Xiao Yang
2018-01-12 6:16 ` [PATCH v2 1/2] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-12 6:16 ` [PATCH v2 2/2] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-12 7:49 ` Eryu Guan
2018-01-12 8:36 ` Dave Chinner
2018-01-12 8:50 ` Eryu Guan
2018-01-12 16:41 ` Darrick J. Wong
2018-01-13 2:23 ` Dave Chinner
2018-01-15 6:29 ` Eryu Guan
2018-01-15 7:48 ` [PATCH v3 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-15 7:48 ` [PATCH v3 2/3] common/filter: factor out expected XFS warnings for mount xiao yang
2018-01-15 7:48 ` [PATCH v3 3/3] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-15 12:45 ` [PATCH v2 2/2] " Brian Foster
2018-01-15 21:03 ` Dave Chinner
2018-01-16 4:02 ` Eryu Guan
2018-01-16 6:41 ` Xiao Yang
2018-01-16 7:26 ` [PATCH v4 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-16 7:26 ` [PATCH v4 2/3] common/filter: factor out expected XFS warnings for mount xiao yang
2018-01-18 8:48 ` Eryu Guan
2018-01-18 8:56 ` Xiao Yang
2018-01-16 7:26 ` [PATCH v4 3/3] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-18 8:46 ` Eryu Guan
2018-01-18 10:49 ` [PATCH v5 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db xiao yang
2018-01-18 10:49 ` [PATCH v5 2/3] common/filter: Factor out expected XFS warnings for assert xiao yang
2018-01-18 18:29 ` Darrick J. Wong
2018-01-19 2:51 ` Eryu Guan
2018-01-19 4:04 ` Xiao Yang
2018-01-19 5:38 ` [PATCH v6 2/3] common: Add _require_no_xfs_bug_on_assert && Factor out filter_xfs_dmesg xiao yang
2018-01-19 5:38 ` [PATCH v6 3/3] xfs: Regression test for invalid sb_logsunit xiao yang
2018-01-18 10:49 ` [PATCH v5 " xiao yang
2018-01-18 18:19 ` [PATCH v5 1/3] common/xfs: Check if write supports [-c|-d] option in xfs_db Darrick J. Wong
2018-01-16 8:50 ` [PATCH v2 2/2] xfs: Regression test for invalid sb_logsunit Dave Chinner
2018-01-16 14:09 ` Brian Foster
2018-01-18 8:44 ` Eryu Guan
2018-01-16 13:58 ` Brian Foster
2018-01-12 7:44 ` [PATCH v2 1/2] common/xfs: Check if write supports [-c|-d] option in xfs_db Eryu Guan
2018-01-12 16:43 ` Darrick J. Wong [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=20180112164327.GG5606@magnolia \
--to=darrick.wong@oracle.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=yangx.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