All of
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <>
To: "Darrick J. Wong" <>
Subject: Re: [PATCH 0/2] xfs test excluses needed for realtime_28k_logdev
Date: Wed, 6 Jul 2022 10:41:09 -0400	[thread overview]
Message-ID: <YsWfBbe/> (raw)
In-Reply-To: <YsS6PQiy+4SPavpA@magnolia>

On Tue, Jul 05, 2022 at 03:25:01PM -0700, Darrick J. Wong wrote:
> On Wed, Jun 29, 2022 at 08:52:05AM -0400, Theodore Ts'o wrote:
> > These are tests in my out-of-tree patches to xfstests, which were
> > cherry-picked from Darrick's out-of-tree patches.  They are needed to
> > prevent a huge whackload (that's a technical term) of test failures in
> > the xfs/realtime_28k_logdev test config, which uses:
> > 
> > XFS_MKFS_OPTIONS='-d rtinherit=1 -m reflink=0,rmapbt=0 -r extsize=28k '
> > 
> > and uses an external logdevice as well as an external realtime device.
> > 
> > This test config is being used in the xfs 5.15 backports testing,
> > since it's one of Darrick's upstream acceptance test configs.
> > 
> > Darrick, any objections if I ask Zorro to consider these for upstream
> > xfstests?
> Hmm, maybe I should post the most recent version of this.  Ok, I'll move
> towards upstream head and send it in a day or two.

Many thanks!

I'll be on the lookout of your patches and drop the older versions of
the aptch (from November 2021) from my tree once they show up.

    	  		       	       - Ted

      reply	other threads:[~2022-07-06 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 12:52 [PATCH 0/2] xfs test excluses needed for realtime_28k_logdev Theodore Ts'o
2022-06-29 12:52 ` [PATCH 1/2] misc: skip remap/fallocate tests when op length not congruent with file allocation unit Theodore Ts'o
2022-06-29 12:52 ` [PATCH 2/2] misc: skip extent size hint tests when hint " Theodore Ts'o
2022-07-05 22:25 ` [PATCH 0/2] xfs test excluses needed for realtime_28k_logdev Darrick J. Wong
2022-07-06 14:41   ` Theodore Ts'o [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YsWfBbe/ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.