FS/XFS testing framework
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, zlang@redhat.com
Cc: linux-xfs@vger.kernel.org, guan@eryu.me, fstests@vger.kernel.org
Subject: [PATCH 2/2] xfs/604: add missing falloc test
Date: Mon, 20 Nov 2023 11:35:20 -0800	[thread overview]
Message-ID: <170050892015.536459.5750821914760062267.stgit@frogsfrogsfrogs> (raw)
In-Reply-To: <170050890870.536459.4420904342934916414.stgit@frogsfrogsfrogs>

From: Darrick J. Wong <djwong@kernel.org>

This test requires both the xfs_io falloc and fpunch commands to run.
falloc isn't supported on alwayscow=1 mounts, which means this test
fails there.

While we're at it, update the commit id since the fix was committed to
6.7-rc2.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>
---
 tests/xfs/604 |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)


diff --git a/tests/xfs/604 b/tests/xfs/604
index 50cdebcd50..bb6db797e5 100755
--- a/tests/xfs/604
+++ b/tests/xfs/604
@@ -13,9 +13,10 @@ _begin_fstest auto prealloc punch
 
 _supported_fs xfs
 _require_scratch
+_require_xfs_io_command "falloc"
 _require_xfs_io_command "fpunch"
 _require_test_program punch-alternating
-_fixed_by_kernel_commit XXXXXXXXXXXX "xfs: fix internal error from AGFL exhaustion"
+_fixed_by_kernel_commit f63a5b3769ad "xfs: fix internal error from AGFL exhaustion"
 
 # Disable the rmapbt so we only need to worry about splitting the bnobt and
 # cntbt at the same time.


  parent reply	other threads:[~2023-11-20 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 19:35 [PATCHSET 0/2] fstests: random fixes for v2023.11.19 Darrick J. Wong
2023-11-20 19:35 ` [PATCH 1/2] xfs/601: move this to tests/generic Darrick J. Wong
2023-11-21  4:35   ` Christoph Hellwig
2023-11-20 19:35 ` Darrick J. Wong [this message]
2023-11-21  4:35   ` [PATCH 2/2] xfs/604: add missing falloc test Christoph Hellwig

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=170050892015.536459.5750821914760062267.stgit@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=guan@eryu.me \
    --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