From: Chandan Babu R <chandanrlinux@gmail.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
darrick.wong@oracle.com
Subject: Re: [PATCH V4 01/11] common/xfs: Add a helper to get an inode fork's extent count
Date: Fri, 05 Mar 2021 20:11:35 +0530 [thread overview]
Message-ID: <87im65u0gw.fsf@garuda> (raw)
In-Reply-To: <20210303173050.GI7269@magnolia>
On 03 Mar 2021 at 23:00, Darrick J. Wong wrote:
> On Mon, Jan 18, 2021 at 11:50:12AM +0530, Chandan Babu R wrote:
>> This commit adds the helper _scratch_get_iext_count() which returns an
>> inode fork's extent count.
>>
>> Signed-off-by: Chandan Babu R <chandanrlinux@gmail.com>
>> ---
>> common/xfs | 22 ++++++++++++++++++++++
>> 1 file changed, 22 insertions(+)
>>
>> diff --git a/common/xfs b/common/xfs
>> index 3f5c14ba..641d6195 100644
>> --- a/common/xfs
>> +++ b/common/xfs
>> @@ -903,6 +903,28 @@ _scratch_get_bmx_prefix() {
>> return 1
>> }
>>
>> +_scratch_get_iext_count()
>> +{
>> + ino=$1
>> + whichfork=$2
>
> Function variables should be declared with 'local' so they don't bleed
> into the global namespace (yay bash!), e.g.
>
> local ino="$1"
Sorry, I forgot about this. I will fix this up.
>
> Also, now that Eric has landed the xfs_db 'path' command upstream, you
> might consider using it:
>
> _scratch_xfs_get_metadata_field "core.nextents" "path /windows/system.ini"
>
In this patchset _scratch_get_iext_count() is being used to get extent counts
of anonymous inodes i.e. inodes which do not have an entry in the filesytem
namespace (e.g. Quota and RT bitmap/summary inodes). Hence the 'path' command
won't be useful in this case.
>> +
>> + case $whichfork in
>> + "attr")
>> + field=core.naextents
>> + ;;
>> + "data")
>> + field=core.nextents
>> + ;;
>> + *)
>> + return 1
>> + esac
>> +
>> + nextents=$(_scratch_xfs_db -c "inode $ino" -c "print $field")
>> + nextents=${nextents##${field} = }
>
> _scratch_xfs_get_metadata_field?
Sure, I will make use of the above mentioned helper.
--
chandan
next prev parent reply other threads:[~2021-03-05 14:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 6:20 [PATCH V4 00/11] xfs: Tests to verify inode fork extent count overflow detection Chandan Babu R
2021-01-18 6:20 ` [PATCH V4 01/11] common/xfs: Add a helper to get an inode fork's extent count Chandan Babu R
2021-03-03 17:30 ` Darrick J. Wong
2021-03-05 14:41 ` Chandan Babu R [this message]
2021-01-18 6:20 ` [PATCH V4 02/11] xfs: Check for extent overflow when trivally adding a new extent Chandan Babu R
2021-03-03 17:38 ` Darrick J. Wong
2021-03-05 14:42 ` Chandan Babu R
2021-01-18 6:20 ` [PATCH V4 03/11] xfs: Check for extent overflow when growing realtime bitmap/summary inodes Chandan Babu R
2021-03-03 17:45 ` Darrick J. Wong
2021-03-04 11:58 ` Chandan Babu R
2021-03-04 16:17 ` Darrick J. Wong
2021-01-18 6:20 ` [PATCH V4 04/11] xfs: Check for extent overflow when punching a hole Chandan Babu R
2021-03-03 17:54 ` Darrick J. Wong
2021-01-18 6:20 ` [PATCH V4 05/11] xfs: Check for extent overflow when adding/removing xattrs Chandan Babu R
2021-03-03 17:56 ` Darrick J. Wong
2021-01-18 6:20 ` [PATCH V4 06/11] xfs: Check for extent overflow when adding/removing dir entries Chandan Babu R
2021-03-03 18:01 ` Darrick J. Wong
2021-03-04 12:22 ` Chandan Babu R
2021-01-18 6:20 ` [PATCH V4 07/11] xfs: Check for extent overflow when writing to unwritten extent Chandan Babu R
2021-03-03 18:05 ` Darrick J. Wong
2021-03-05 14:43 ` Chandan Babu R
2021-01-18 6:20 ` [PATCH V4 08/11] xfs: Check for extent overflow when moving extent from cow to data fork Chandan Babu R
2021-03-03 18:07 ` Darrick J. Wong
2021-01-18 6:20 ` [PATCH V4 09/11] xfs: Check for extent overflow when remapping an extent Chandan Babu R
2021-03-03 18:09 ` Darrick J. Wong
2021-01-18 6:20 ` [PATCH V4 10/11] xfs: Check for extent overflow when swapping extents Chandan Babu R
2021-03-03 18:10 ` Darrick J. Wong
2021-01-18 6:20 ` [PATCH V4 11/11] xfs: Stress test with bmap_alloc_minlen_extent error tag enabled Chandan Babu R
2021-03-03 18:12 ` Darrick J. Wong
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=87im65u0gw.fsf@garuda \
--to=chandanrlinux@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=djwong@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).