Linux-XFS Archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, zlang@redhat.com
Cc: Christoph Hellwig <hch@lst.de>,
	David Hildenbrand <david@redhat.com>,
	fstests@vger.kernel.org, linux-xfs@vger.kernel.org, guan@eryu.me
Subject: [PATCHSET] fstests: random fixes for v2024.02.09
Date: Tue, 26 Mar 2024 19:43:17 -0700	[thread overview]
Message-ID: <171150739778.3286541.16038231600708193472.stgit@frogsfrogsfrogs> (raw)

Hi all,

Here's the usual odd fixes for fstests.  Most of these are cleanups and
bug fixes that have been aging in my djwong-wtf branch forever.

If you're going to start using this code, I strongly recommend pulling
from my git trees, which are linked below.

This has been running on the djcloud for months with no problems.  Enjoy!
Comments and questions are, as always, welcome.

--D

kernel git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=random-fixes

xfsprogs git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfsprogs-dev.git/log/?h=random-fixes

fstests git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=random-fixes
---
Commits in this patchset:
 * xfs/270: fix rocompat regex
 * xfs/176: fix stupid failure
 * generic/{166,167,333,334,671}: actually fill the filesystem with snapshots
 * generic: test MADV_POPULATE_READ with IO errors
---
 common/reflink         |    8 ++++++
 tests/generic/166      |    2 +
 tests/generic/167      |    2 +
 tests/generic/1835     |   65 ++++++++++++++++++++++++++++++++++++++++++++++++
 tests/generic/1835.out |    4 +++
 tests/generic/333      |    2 +
 tests/generic/334      |    2 +
 tests/generic/671      |    2 +
 tests/xfs/176          |    2 +
 tests/xfs/270          |    3 +-
 10 files changed, 85 insertions(+), 7 deletions(-)
 create mode 100755 tests/generic/1835
 create mode 100644 tests/generic/1835.out


             reply	other threads:[~2024-03-27  2:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27  2:43 Darrick J. Wong [this message]
2024-03-27  2:43 ` [PATCH 1/4] xfs/270: fix rocompat regex Darrick J. Wong
2024-03-27  2:48   ` [PATCH v1.1 " Darrick J. Wong
2024-03-27 11:32     ` Christoph Hellwig
2024-03-27  2:43 ` [PATCH 2/4] xfs/176: fix stupid failure Darrick J. Wong
2024-03-27 11:32   ` Christoph Hellwig
2024-03-27  2:43 ` [PATCH 3/4] generic/{166,167,333,334,671}: actually fill the filesystem with snapshots Darrick J. Wong
2024-03-27 16:59   ` Christoph Hellwig
2024-03-29 23:07     ` Darrick J. Wong
2024-03-30  5:39       ` Christoph Hellwig
2024-03-30  7:14     ` Zorro Lang
2024-03-27  2:43 ` [PATCH 4/4] generic: test MADV_POPULATE_READ with IO errors Darrick J. Wong
2024-03-30  7:12   ` Zorro Lang
2024-03-30 15:31     ` Darrick J. Wong
  -- strict thread matches above, loose matches on Subject: below --
2024-02-27  2:00 [PATCHSET] fstests: random fixes for v2024.02.09 Darrick J. Wong
2024-03-03 13:34 ` Zorro Lang
2024-03-07 23:18   ` 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=171150739778.3286541.16038231600708193472.stgit@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=david@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=guan@eryu.me \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).