FS/XFS testing framework
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: fstests@vger.kernel.org
Subject: Re: [PATCH] ext4/054,ext4/055: don't run when using DAX
Date: Wed, 27 Apr 2022 10:53:24 -0400	[thread overview]
Message-ID: <YmlY5NhDodhRRpkU@mit.edu> (raw)
In-Reply-To: <20220427080540.o7tu3nz6g5ch6xpt@zlang-mailbox>

On Wed, Apr 27, 2022 at 04:05:40PM +0800, Zorro Lang wrote:
> 
> "The DAX code currently only supports files with a block size equal to your
> kernel's PAGE_SIZE" [1], so I suppose any cases with smaller blocksize (< pagesize)
> should "_exclude_scratch_mount_option dax".
> 
> And if this supposition is right, we'd better do "skipping dax testing if blocksize
> is less than pagesize" in a common helper. Good news is we have _scratch_mkfs_blocksized.
> So how about do:
>   if [ $blocksize < $pagesize ];then
>       _exclude_scratch_mount_option dax
>   fi
> in _scratch_mkfs_blocksized? then let ext4/054 and ext4/055 turn to use _scratch_mkfs_blocksized.

That's a good thing to and it would work for ext4/054 and ext/022
(which already uses "_exclude_scratch_mount_option dax" and
"_scratch_mkfs").  However, a number of other tests, including
ext4/055 and ext4/035 need to give additional parameters to mfks, such
as "-O quota" or "-E resize=262144".

So _scratch_mkfs_blocksized isn't always going to work for tests in
ext4/* where we often are passing ext4-specific mkfs options to
mkfs.ext4.

So I can add your suggestion to _scratch_mkfs_blocksized, and use that
for ext4/054, but it's not going to be a solution for ext4/055.

Cheers,

						- Ted

  reply	other threads:[~2022-04-27 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27  0:52 [PATCH] ext4/054,ext4/055: don't run when using DAX Theodore Ts'o
2022-04-27  8:05 ` Zorro Lang
2022-04-27 14:53   ` Theodore Ts'o [this message]
2022-04-27 17:19     ` Zorro Lang
2022-04-27 19:44       ` Theodore Ts'o
2022-04-28  4:53         ` Zorro Lang
2022-04-28  5:58           ` Dave Chinner
2022-04-28  6:55             ` Zorro Lang
2022-04-29  1:10 ` 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=YmlY5NhDodhRRpkU@mit.edu \
    --to=tytso@mit.edu \
    --cc=fstests@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