From: Nirjhar Roy <nirjhar@linux.ibm.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org, ritesh.list@gmail.com,
ojaswin@linux.ibm.com, zlang@kernel.org
Subject: Re: [PATCH v3 1/3] common/rc,xfs/207: Add a common helper function to check xflag bits
Date: Fri, 22 Nov 2024 00:00:52 +0530 [thread overview]
Message-ID: <8ad602fa-119c-4863-a3be-e778fefa0b1c@linux.ibm.com> (raw)
In-Reply-To: <20241121172029.GX9425@frogsfrogsfrogs>
On 11/21/24 22:50, Darrick J. Wong wrote:
> On Thu, Nov 21, 2024 at 10:39:10AM +0530, Nirjhar Roy wrote:
>> This patch defines a common helper function to test whether any of
>> fsxattr xflags field is set or not. We will use this helper in
>> an upcoming patch for checking extsize (e) flag.
>>
>> Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
>> Reviewed-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
>> Signed-off-by: Nirjhar Roy <nirjhar@linux.ibm.com>
> Looks good to me now,
> Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
>
> --D
Thank you.
--NR
>
>> ---
>> common/rc | 7 +++++++
>> tests/xfs/207 | 15 ++++-----------
>> 2 files changed, 11 insertions(+), 11 deletions(-)
>>
>> diff --git a/common/rc b/common/rc
>> index 2af26f23..cccc98f5 100644
>> --- a/common/rc
>> +++ b/common/rc
>> @@ -41,6 +41,13 @@ _md5_checksum()
>> md5sum $1 | cut -d ' ' -f1
>> }
>>
>> +# Check whether a fsxattr xflags name ($2) field is set on a given file ($1).
>> +# e.g, fsxattr.xflags = 0x80000800 [extsize, has-xattr]
>> +_test_fsxattr_xflag()
>> +{
>> + grep -q "fsxattr.xflags.*\[.*$2.*\]" <($XFS_IO_PROG -c "stat -v" "$1")
>> +}
>> +
>> # Write a byte into a range of a file
>> _pwrite_byte() {
>> local pattern="$1"
>> diff --git a/tests/xfs/207 b/tests/xfs/207
>> index bbe21307..394e7e55 100755
>> --- a/tests/xfs/207
>> +++ b/tests/xfs/207
>> @@ -21,15 +21,6 @@ _require_cp_reflink
>> _require_xfs_io_command "fiemap"
>> _require_xfs_io_command "cowextsize"
>>
>> -# Takes the fsxattr.xflags line,
>> -# i.e. fsxattr.xflags = 0x0 [--------------C-]
>> -# and tests whether a flag character is set
>> -test_xflag()
>> -{
>> - local flg=$1
>> - grep -q "\[.*${flg}.*\]" && echo "$flg flag set" || echo "$flg flag unset"
>> -}
>> -
>> echo "Format and mount"
>> _scratch_mkfs > $seqres.full 2>&1
>> _scratch_mount >> $seqres.full 2>&1
>> @@ -65,14 +56,16 @@ echo "Set cowextsize and check flag"
>> $XFS_IO_PROG -c "cowextsize 1048576" $testdir/file3 | _filter_scratch
>> _scratch_cycle_mount
>>
>> -$XFS_IO_PROG -c "stat" $testdir/file3 | grep 'fsxattr.xflags' | test_xflag "C"
>> +_test_fsxattr_xflag "$testdir/file3" "cowextsize" && echo "C flag set" || \
>> + echo "C flag unset"
>> $XFS_IO_PROG -c "cowextsize" $testdir/file3 | _filter_scratch
>>
>> echo "Unset cowextsize and check flag"
>> $XFS_IO_PROG -c "cowextsize 0" $testdir/file3 | _filter_scratch
>> _scratch_cycle_mount
>>
>> -$XFS_IO_PROG -c "stat" $testdir/file3 | grep 'fsxattr.xflags' | test_xflag "C"
>> +_test_fsxattr_xflag "$testdir/file3" "cowextsize" && echo "C flag set" || \
>> + echo "C flag unset"
>> $XFS_IO_PROG -c "cowextsize" $testdir/file3 | _filter_scratch
>>
>> status=0
>> --
>> 2.43.5
>>
>>
--
---
Nirjhar Roy
Linux Kernel Developer
IBM, Bangalore
next prev parent reply other threads:[~2024-11-21 18:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 5:09 [PATCH v3 0/3] Addition of new tests for extsize hints Nirjhar Roy
2024-11-21 5:09 ` [PATCH v3 1/3] common/rc,xfs/207: Add a common helper function to check xflag bits Nirjhar Roy
2024-11-21 17:20 ` Darrick J. Wong
2024-11-21 18:30 ` Nirjhar Roy [this message]
2024-11-21 5:09 ` [PATCH v3 2/3] common/rc: Add a new _require_scratch_extsize helper function Nirjhar Roy
2024-11-21 7:53 ` Ritesh Harjani
2024-11-21 18:33 ` Nirjhar Roy
2024-11-21 18:52 ` Ritesh Harjani
2024-11-22 16:04 ` Darrick J. Wong
2024-11-22 18:07 ` Nirjhar Roy
2024-11-22 18:44 ` Darrick J. Wong
2024-11-22 19:06 ` Nirjhar Roy
2024-11-21 5:09 ` [PATCH v3 3/3] generic: Addition of new tests for extsize hints Nirjhar Roy
2024-11-21 17:27 ` Darrick J. Wong
2024-11-21 18:34 ` Nirjhar Roy
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=8ad602fa-119c-4863-a3be-e778fefa0b1c@linux.ibm.com \
--to=nirjhar@linux.ibm.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=zlang@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;
as well as URLs for NNTP newsgroup(s).