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,
djwong@kernel.org
Subject: [PATCH V3 00/11] xfs: Tests to verify inode fork extent count overflow detection
Date: Tue, 12 Jan 2021 13:10:16 +0530 [thread overview]
Message-ID: <20210112074027.10311-1-chandanrlinux@gmail.com> (raw)
The patchset at
https://lore.kernel.org/linux-xfs/20210110160720.3922965-1-chandanrlinux@gmail.com/T/
added support for XFS to detect inode extent count overflow when
performing various filesystem operations. The patchset also added
new error injection tags for,
1. Reducing maximum extent count to 10.
2. Allocating only single block sized extents.
The corresponding code for xfsprogs can be obtained from
https://lore.kernel.org/linux-xfs/20201104114900.172147-1-chandanrlinux@gmail.com/.
The patches posted along with this cover letter add tests to verify
the correctness of in-kernel inode extent count overflow detection
mechanism.
These patches can also be obtained from
https://github.com/chandanr/xfstests.git at branch
extent-overflow-tests.
Changelog:
V2 -> V3:
1. Kernel's max pseudo extent count is once again set to 10. Hence
change the tests back to using 10 as the maximum extent count.
2. The following tests associated with directories have been removed
since directory remove and rename operations are not expected to
fail (with -EFBIG error code) in low inode extent count
scenarios:
- Populate source directory and mv one entry to destination
directory.
- Populate a directory and remove one entry.
V1 -> V2:
1. Obtain extent count for inodes accessible through filesystem path
names via "xfs_io -c 'stat' ..." command line. This gets rid of
unmount/mount cycles from most of the tests.
2. Use _fill_fs() to consume free space of a filesystem.
3. Use _scratch_inject_error() helper to enable/disable error tags.
4. Use sizeof(struct xfs_dqblk) to calculate number of quotas inside
one filesystem block.
5. Write once to every block of the quota inode instead of
sequentially filling up each block.
6. Use _get_file_block_size() for tests involving regular files.
7. Modify tests to suit the new pseudo max extent count of 35.
8. Replace xfs_io with $XFS_IO_PROG.
9. Remove code that extended a realtime file since this takes the
same path as direct I/O to a regular file.
10. For xattr, do not execute test script when block size is < 4k.
11. Add code to test if removing an xattr from a full attribute fork
succeeds.
12. Add code to test if removing a file whose attribute fork is full
succeeds.
13. Add code to test if removing a entry from a full directory
succeeds.
14. Add code to test if removing a full directory succeeds.
15. Writing to unwritten extents: Integrate buffered and direct I/O
tests into a for loop.
16. Writing to a shared extent test: Add test to check funshare
operation.
17. Use _scale_fsstress_args() to scale values for "-p" and "-n"
arguments for fsstress.
Chandan Babu R (11):
common/xfs: Add a helper to get an inode fork's extent count
xfs: Check for extent overflow when trivally adding a new extent
xfs: Check for extent overflow when growing realtime bitmap/summary
inodes
xfs: Check for extent overflow when punching a hole
xfs: Check for extent overflow when adding/removing xattrs
xfs: Check for extent overflow when adding/removing dir entries
xfs: Check for extent overflow when writing to unwritten extent
xfs: Check for extent overflow when moving extent from cow to data
fork
xfs: Check for extent overflow when remapping an extent
xfs: Check for extent overflow when swapping extents
xfs: Stress test with bmap_alloc_minlen_extent error tag enabled
common/xfs | 22 ++++++
tests/xfs/522 | 173 ++++++++++++++++++++++++++++++++++++++++++
tests/xfs/522.out | 20 +++++
tests/xfs/523 | 119 +++++++++++++++++++++++++++++
tests/xfs/523.out | 11 +++
tests/xfs/524 | 84 +++++++++++++++++++++
tests/xfs/524.out | 19 +++++
tests/xfs/525 | 141 +++++++++++++++++++++++++++++++++++
tests/xfs/525.out | 18 +++++
tests/xfs/526 | 186 ++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/526.out | 17 +++++
tests/xfs/527 | 89 ++++++++++++++++++++++
tests/xfs/527.out | 11 +++
tests/xfs/528 | 110 +++++++++++++++++++++++++++
tests/xfs/528.out | 12 +++
tests/xfs/529 | 82 ++++++++++++++++++++
tests/xfs/529.out | 8 ++
tests/xfs/530 | 109 +++++++++++++++++++++++++++
tests/xfs/530.out | 13 ++++
tests/xfs/531 | 84 +++++++++++++++++++++
tests/xfs/531.out | 7 ++
tests/xfs/group | 10 +++
22 files changed, 1345 insertions(+)
create mode 100755 tests/xfs/522
create mode 100644 tests/xfs/522.out
create mode 100755 tests/xfs/523
create mode 100644 tests/xfs/523.out
create mode 100755 tests/xfs/524
create mode 100644 tests/xfs/524.out
create mode 100755 tests/xfs/525
create mode 100644 tests/xfs/525.out
create mode 100755 tests/xfs/526
create mode 100644 tests/xfs/526.out
create mode 100755 tests/xfs/527
create mode 100644 tests/xfs/527.out
create mode 100755 tests/xfs/528
create mode 100644 tests/xfs/528.out
create mode 100755 tests/xfs/529
create mode 100644 tests/xfs/529.out
create mode 100755 tests/xfs/530
create mode 100644 tests/xfs/530.out
create mode 100755 tests/xfs/531
create mode 100644 tests/xfs/531.out
--
2.29.2
next reply other threads:[~2021-01-12 7:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 7:40 Chandan Babu R [this message]
2021-01-12 7:40 ` [PATCH V3 01/11] common/xfs: Add a helper to get an inode fork's extent count Chandan Babu R
2021-01-12 7:40 ` [PATCH V3 02/11] xfs: Check for extent overflow when trivally adding a new extent Chandan Babu R
2021-01-12 7:40 ` [PATCH V3 03/11] xfs: Check for extent overflow when growing realtime bitmap/summary inodes Chandan Babu R
2021-01-12 7:40 ` [PATCH V3 04/11] xfs: Check for extent overflow when punching a hole Chandan Babu R
2021-01-12 7:40 ` [PATCH V3 05/11] xfs: Check for extent overflow when adding/removing xattrs Chandan Babu R
2021-01-12 7:40 ` [PATCH V3 06/11] xfs: Check for extent overflow when adding/removing dir entries Chandan Babu R
2021-01-12 7:40 ` [PATCH V3 07/11] xfs: Check for extent overflow when writing to unwritten extent Chandan Babu R
2021-01-12 7:40 ` [PATCH V3 08/11] xfs: Check for extent overflow when moving extent from cow to data fork Chandan Babu R
2021-01-12 7:40 ` [PATCH V3 09/11] xfs: Check for extent overflow when remapping an extent Chandan Babu R
2021-01-12 7:40 ` [PATCH V3 10/11] xfs: Check for extent overflow when swapping extents Chandan Babu R
2021-01-12 7:40 ` [PATCH V3 11/11] xfs: Stress test 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=20210112074027.10311-1-chandanrlinux@gmail.com \
--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 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.