FS/XFS testing framework
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 1/2] ext4/045: skip test if the block size is 1k
Date: Tue, 11 Jun 2024 17:40:49 +0100	[thread overview]
Message-ID: <20240611164049.GG4182@mit.edu> (raw)
In-Reply-To: <20240611142754.GF52977@frogsfrogsfrogs>

On Tue, Jun 11, 2024 at 07:27:54AM -0700, Darrick J. Wong wrote:
> On Tue, Jun 11, 2024 at 04:58:52AM -0400, Theodore Ts'o wrote:
> > If the file system is 1k, this test will fail because with dir_index
> > enabled, the directory tree will get too deep, and the kernel will
> > return ENOSPC and log the EXT4-fs warning "Directory (ino: NNN) index
> > full, reach max htree level: 2".  So if the blocksize is less than 2k,
> > _notrun this test.
> 
> Didn't ext4 recently gain support for 3-level htrees?

Ext4 has support for a while, but it's an optional feature which is
not enabled by default.  I suppose we could try to set the feature,
and skip the test if the kernel doesn't support it.  (Or decide that
no one cares about RHEL7, and just YOLO, since who else still cares
about kernels older than 4.13?  :-)

I'm just not sure whether it's worth the extra complexity to do it,
but for those people who care about code coverage statistics, it would
help a tiny amount....

						- Ted

      reply	other threads:[~2024-06-11 16:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  8:58 [PATCH 1/2] ext4/045: skip test if the block size is 1k Theodore Ts'o
2024-06-11  8:58 ` [PATCH 2/2] generic/455: skip the test if the file system doesn't support journaling Theodore Ts'o
2024-06-11 14:27   ` Darrick J. Wong
2024-06-11 22:26     ` Theodore Ts'o
2024-06-11 14:27 ` [PATCH 1/2] ext4/045: skip test if the block size is 1k Darrick J. Wong
2024-06-11 16:40   ` 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:
  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=20240611164049.GG4182@mit.edu \
    --to=tytso@mit.edu \
    --cc=djwong@kernel.org \
    --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