From: Zorro Lang <zlang@redhat.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs/021: filter out detailed array element info from xfs_db
Date: Thu, 10 Nov 2016 12:33:36 +0800 [thread overview]
Message-ID: <20161110043336.GE3327@dhcp12-143.nay.redhat.com> (raw)
In-Reply-To: <1478752183-27499-1-git-send-email-eguan@redhat.com>
On Thu, Nov 10, 2016 at 12:29:43PM +0800, Eryu Guan wrote:
> Starting from xfsprogs commit 384283555871 ("xfs_db: print one array
> element per line"), xfs_db prints one array element per line. This
> breaks the filter in xfs/021, which now fails as:
>
> hdr.freemap[0-2] = [base,size] [FREEMAP..]
> +0:[104,1892]
> +1:[0,0]
> +2:[0,0]
> entries[0-2] = [hashval,nameidx,incomplete,root,local] [ENTRIES..]
>
> So we have extra lines that need to be filtered out,
>
> Signed-off-by: Eryu Guan <eguan@redhat.com>
> ---
V2 looks better to me,
Reviewed-by: Zorro Lang <zlang@redhat.com>
> - be more precise on matching the array output, address Zorro's comment
>
> tests/xfs/021 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/xfs/021 b/tests/xfs/021
> index 67a4346..0471b95 100755
> --- a/tests/xfs/021
> +++ b/tests/xfs/021
> @@ -151,7 +151,7 @@ s/^(hdr.info.magic =) 0x3bee/\1 0xfbee/;
> s/^(hdr.firstused =) (\d+)/\1 FIRSTUSED/;
> s/^(hdr.freemap\[0-2] = \[base,size]).*/\1 [FREEMAP..]/;
> s/^(entries\[0-2] = \[hashval,nameidx,incomplete,root,local]).*/\1 [ENTRIES..]/;
> - print;'
> + print unless /^\d+:\[.*/;'
>
> echo "*** done"
> exit
> --
> 2.7.4
>
> --
> 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
next prev parent reply other threads:[~2016-11-10 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 4:29 [PATCH v2] xfs/021: filter out detailed array element info from xfs_db Eryu Guan
2016-11-10 4:33 ` Zorro Lang [this message]
2016-11-13 12:29 ` Christoph Hellwig
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=20161110043336.GE3327@dhcp12-143.nay.redhat.com \
--to=zlang@redhat.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@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