From: Chandan Babu R <chandanrlinux@gmail.com>
To: fstests@vger.kernel.org
Cc: Chandan Babu R <chandanrlinux@gmail.com>,
linux-xfs@vger.kernel.org, darrick.wong@oracle.com
Subject: [PATCH V2 01/11] common/xfs: Add a helper to get an inode fork's extent count
Date: Sat, 21 Nov 2020 13:53:22 +0530 [thread overview]
Message-ID: <20201121082332.89739-2-chandanrlinux@gmail.com> (raw)
In-Reply-To: <20201121082332.89739-1-chandanrlinux@gmail.com>
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
+
+ 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} = }
+
+ echo $nextents
+}
+
#
# Ensures that we don't pass any mount options incompatible with XFS v4
#
--
2.29.2
next prev parent reply other threads:[~2020-11-21 8:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 8:23 [PATCH V2 00/11] xfs: Tests to check for inode fork extent count overflow detection Chandan Babu R
2020-11-21 8:23 ` Chandan Babu R [this message]
2020-11-21 8:23 ` [PATCH V2 02/11] xfs: Check for extent overflow when trivally adding a new extent Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 03/11] xfs: Check for extent overflow when growing realtime bitmap/summary inodes Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 04/11] xfs: Check for extent overflow when punching a hole Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 05/11] xfs: Check for extent overflow when adding/removing xattrs Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 06/11] xfs: Check for extent overflow when adding/removing dir entries Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 07/11] xfs: Check for extent overflow when writing to unwritten extent Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 08/11] xfs: Check for extent overflow when moving extent from cow to data fork Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 09/11] xfs: Check for extent overflow when remapping an extent Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 10/11] xfs: Check for extent overflow when swapping extents Chandan Babu R
2020-11-21 8:23 ` [PATCH V2 11/11] xfs: Stress test with with bmap_alloc_minlen_extent error tag enabled Chandan Babu R
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=20201121082332.89739-2-chandanrlinux@gmail.com \
--to=chandanrlinux@gmail.com \
--cc=darrick.wong@oracle.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 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.