public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: zlang@kernel.org, fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs/233: don't require rmap
Date: Mon, 29 Jul 2024 09:41:07 -0700	[thread overview]
Message-ID: <20240729164107.GB6352@frogsfrogsfrogs> (raw)
In-Reply-To: <20240729142027.430744-2-hch@lst.de>

On Mon, Jul 29, 2024 at 07:20:27AM -0700, Christoph Hellwig wrote:
> Nothing in xfs/233 requires an rmap, it can run on any file system.
> And it is a very useful test because it starts out with a very small
> file system (or RT subvolume), which exercise some code paths no other
> test does.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Heh, you're right.  Lets do this! :)

Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D

> ---
>  tests/xfs/233 | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/tests/xfs/233 b/tests/xfs/233
> index 5d2c10e7d..211e5f842 100755
> --- a/tests/xfs/233
> +++ b/tests/xfs/233
> @@ -4,7 +4,7 @@
>  #
>  # FS QA Test No. 233
>  #
> -# Tests xfs_growfs on a rmapbt filesystem
> +# Tests xfs_growfs starting with a really small file system.
>  #
>  . ./common/preamble
>  _begin_fstest auto quick rmap growfs
> @@ -12,7 +12,6 @@ _begin_fstest auto quick rmap growfs
>  # Import common functions.
>  . ./common/filter
>  
> -_require_xfs_scratch_rmapbt
>  _require_no_large_scratch_dev
>  
>  echo "Format and mount"
> -- 
> 2.43.0
> 
> 

  reply	other threads:[~2024-07-29 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 14:20 [PATCH 1/2] add more tests to the growfs group Christoph Hellwig
2024-07-29 14:20 ` [PATCH 2/2] xfs/233: don't require rmap Christoph Hellwig
2024-07-29 16:41   ` Darrick J. Wong [this message]
2024-07-29 16:40 ` [PATCH 1/2] add more tests to the growfs group 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=20240729164107.GB6352@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@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