From: Xiao Yang <yangx.jy@fujitsu.com>
To: "Darrick J. Wong" <djwong@kernel.org>, <zlang@redhat.com>
Cc: <linux-xfs@vger.kernel.org>, <fstests@vger.kernel.org>, <guan@eryu.me>
Subject: Re: [PATCH 1/3] xfs: fix dax inode flag test failures
Date: Wed, 18 Jan 2023 14:55:18 +0800 [thread overview]
Message-ID: <c59abe2c-9c2f-1181-480e-40222b1f6886@fujitsu.com> (raw)
In-Reply-To: <167400102458.1914858.6889539595788984119.stgit@magnolia>
Hi Darrick,
It looks good to me.
Reviewed-by: Xiao Yang <yangx.jy@fujitsu.com>
Best Regards,
Xiao Yang
On 2023/1/18 8:42, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Filter out the DAX inode flag because it's causing problems with this
> test.
>
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> ---
> tests/xfs/128 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
> diff --git a/tests/xfs/128 b/tests/xfs/128
> index 5591342d41..8c1663c6c5 100755
> --- a/tests/xfs/128
> +++ b/tests/xfs/128
> @@ -81,7 +81,7 @@ c13=$(_md5_checksum $testdir/file3)
> c14=$(_md5_checksum $testdir/file4)
>
> echo "Defragment"
> -lsattr -l $testdir/ | _filter_scratch | _filter_spaces
> +lsattr -l $testdir/ | _filter_scratch | _filter_spaces | sed -e 's/DAX/---/g'
> $XFS_FSR_PROG -v -d $testdir/file1 >> $seqres.full
> $XFS_FSR_PROG -v -d $testdir/file2 >> $seqres.full # fsr probably breaks the link
> $XFS_FSR_PROG -v -d $testdir/file3 >> $seqres.full # fsr probably breaks the link
>
next prev parent reply other threads:[~2023-01-18 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 0:41 [PATCHSET 0/3] fstests: fix dax+reflink tests Darrick J. Wong
2023-01-18 0:42 ` [PATCH 1/3] xfs: fix dax inode flag test failures Darrick J. Wong
2023-01-18 6:55 ` Xiao Yang [this message]
2023-01-18 0:42 ` [PATCH 2/3] xfs: fix reflink test failures when dax is enabled Darrick J. Wong
2023-01-18 5:10 ` Xiao Yang
2023-01-18 0:42 ` [PATCH 3/3] xfs/182: fix spurious direct write failure Darrick J. Wong
2023-01-18 5:13 ` Xiao 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=c59abe2c-9c2f-1181-480e-40222b1f6886@fujitsu.com \
--to=yangx.jy@fujitsu.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.