From: Chandan Babu R <chandanrlinux@gmail.com>
To: fstests@vger.kernel.org
Cc: linux-xfs@vger.kernel.org, darrick.wong@oracle.com
Subject: Re: [PATCH 00/11] xfs: Tests to check for inode fork extent count overflow detection
Date: Fri, 13 Nov 2020 16:59:18 +0530 [thread overview]
Message-ID: <15437715.NU04MGavY6@garuda> (raw)
In-Reply-To: <20201113112704.28798-1-chandanrlinux@gmail.com>
On Friday 13 November 2020 4:56:52 PM IST Chandan Babu R wrote:
> The patchset at
> https://lore.kernel.org/linux-xfs/20201103150642.2032284-1-chandanrlinux@gmail.com/T/#m90a8754df516bbd0c36830904a2e31c37983792c
> added support to 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 if
> the in-kernel inode extent count overflow detection mechanism works
> correctly.
>
> These patches can also be obtained from
> https://github.com/chandanr/xfsprogs-dev.git at branch
> extent-overflow-tests.
Sorry, the correct git repository URL is
https://github.com/chandanr/xfstests.git.
>
> 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 trivally adding a new extent
> 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 with bmap_alloc_minlen_extent error tag enabled
>
> common/xfs | 22 +++
> tests/xfs/522 | 214 +++++++++++++++++++++++++++
> tests/xfs/522.out | 24 ++++
> tests/xfs/523 | 176 +++++++++++++++++++++++
> tests/xfs/523.out | 18 +++
> tests/xfs/524 | 210 +++++++++++++++++++++++++++
> tests/xfs/524.out | 25 ++++
> tests/xfs/525 | 154 ++++++++++++++++++++
> tests/xfs/525.out | 16 +++
> tests/xfs/526 | 360 ++++++++++++++++++++++++++++++++++++++++++++++
> tests/xfs/526.out | 47 ++++++
> tests/xfs/527 | 125 ++++++++++++++++
> tests/xfs/527.out | 13 ++
> tests/xfs/528 | 87 +++++++++++
> tests/xfs/528.out | 8 ++
> tests/xfs/529 | 86 +++++++++++
> tests/xfs/529.out | 8 ++
> tests/xfs/530 | 115 +++++++++++++++
> tests/xfs/530.out | 13 ++
> tests/xfs/531 | 85 +++++++++++
> tests/xfs/531.out | 6 +
> tests/xfs/group | 10 ++
> 22 files changed, 1822 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
>
>
--
chandan
prev parent reply other threads:[~2020-11-13 12:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 11:26 [PATCH 00/11] xfs: Tests to check for inode fork extent count overflow detection Chandan Babu R
2020-11-13 11:26 ` [PATCH 01/11] common/xfs: Add a helper to get an inode fork's extent count Chandan Babu R
2020-11-14 0:10 ` Darrick J. Wong
2020-11-13 11:26 ` [PATCH 02/11] xfs: Check for extent overflow when trivally adding a new extent Chandan Babu R
2020-11-14 0:24 ` Darrick J. Wong
2020-11-17 14:12 ` Chandan Babu R
2020-11-18 2:30 ` Darrick J. Wong
2020-11-18 4:09 ` Chandan Babu R
2020-11-13 11:26 ` [PATCH 03/11] " Chandan Babu R
2020-11-14 0:18 ` Darrick J. Wong
2020-11-17 14:22 ` Chandan Babu R
2020-11-13 11:26 ` [PATCH 04/11] xfs: Check for extent overflow when punching a hole Chandan Babu R
2020-11-14 0:28 ` Darrick J. Wong
2020-11-17 14:26 ` Chandan Babu R
2020-11-13 11:26 ` [PATCH 05/11] xfs: Check for extent overflow when adding/removing xattrs Chandan Babu R
2020-11-14 0:34 ` Darrick J. Wong
2020-11-17 14:30 ` Chandan Babu R
2020-11-13 11:26 ` [PATCH 06/11] xfs: Check for extent overflow when adding/removing dir entries Chandan Babu R
2020-11-14 0:37 ` Darrick J. Wong
2020-11-17 14:50 ` Chandan Babu R
2020-11-13 11:26 ` [PATCH 07/11] xfs: Check for extent overflow when writing to unwritten extent Chandan Babu R
2020-11-14 0:39 ` Darrick J. Wong
2020-11-17 15:15 ` Chandan Babu R
2020-11-13 11:27 ` [PATCH 08/11] xfs: Check for extent overflow when moving extent from cow to data fork Chandan Babu R
2020-11-14 0:42 ` Darrick J. Wong
2020-11-18 5:20 ` Chandan Babu R
2020-11-13 11:27 ` [PATCH 09/11] xfs: Check for extent overflow when remapping an extent Chandan Babu R
2020-11-14 0:43 ` Darrick J. Wong
2020-11-13 11:27 ` [PATCH 10/11] xfs: Check for extent overflow when swapping extents Chandan Babu R
2020-11-14 0:08 ` Darrick J. Wong
2020-11-17 15:35 ` Chandan Babu R
2020-11-18 2:23 ` Darrick J. Wong
2020-11-13 11:27 ` [PATCH 11/11] xfs: Stress test with with bmap_alloc_minlen_extent error tag enabled Chandan Babu R
2020-11-14 0:06 ` Darrick J. Wong
2020-11-17 15:24 ` Chandan Babu R
2020-11-13 11:29 ` Chandan Babu R [this message]
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=15437715.NU04MGavY6@garuda \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox