From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, guaneryu@gmail.com
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org, guan@eryu.me
Subject: [PATCHSET 0/3] fstests: regression tests for 5.13/5.14 rt fixes
Date: Tue, 27 Jul 2021 17:10:01 -0700 [thread overview]
Message-ID: <162743100128.3428143.7362558731136046380.stgit@magnolia> (raw)
Hi all,
Add regression tests to trigger some bugs in the realtime allocator that
were fixed in kernel 5.13 and 5.14.
If you're going to start using this mess, you probably ought to just
pull from my git trees, which are linked below.
This is an extraordinary way to destroy everything. Enjoy!
Comments and questions are, as always, welcome.
--D
fstests git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=realtime-fixes
---
tests/xfs/774 | 78 +++++++++++++++++++++++++
tests/xfs/774.out | 5 ++
tests/xfs/775 | 165 +++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/775.out | 3 +
tests/xfs/776 | 57 ++++++++++++++++++
tests/xfs/776.out | 5 ++
tests/xfs/779 | 112 ++++++++++++++++++++++++++++++++++++
tests/xfs/779.out | 2 +
8 files changed, 427 insertions(+)
create mode 100755 tests/xfs/774
create mode 100644 tests/xfs/774.out
create mode 100755 tests/xfs/775
create mode 100644 tests/xfs/775.out
create mode 100755 tests/xfs/776
create mode 100644 tests/xfs/776.out
create mode 100755 tests/xfs/779
create mode 100644 tests/xfs/779.out
next reply other threads:[~2021-07-28 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 0:10 Darrick J. Wong [this message]
2021-07-28 0:10 ` [PATCH 1/3] xfs: test fsx with extent size hints set on a realtime file Darrick J. Wong
2021-07-28 0:10 ` [PATCH 2/3] xfs: test correct propagation of rt extent size hints on rtinherit dirs Darrick J. Wong
2021-07-28 0:10 ` [PATCH 3/3] xfs: test adding realtime sections to filesystem Darrick J. Wong
2021-09-01 0:11 [PATCHSET 0/3] fstests: regression tests for 5.13/5.14 rt fixes 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=162743100128.3428143.7362558731136046380.stgit@magnolia \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=guaneryu@gmail.com \
--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).