From: "Theodore Ts'o" <tytso@mit.edu>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 5/8] generic/740: enable by default
Date: Mon, 24 Jun 2024 23:50:08 -0400 [thread overview]
Message-ID: <20240625035008.GC7185@mit.edu> (raw)
In-Reply-To: <20240624161605.GF103020@frogsfrogsfrogs>
On Mon, Jun 24, 2024 at 09:16:05AM -0700, Darrick J. Wong wrote:
> On Sun, Jun 23, 2024 at 02:10:34PM +0200, Christoph Hellwig wrote:
> > Instead of limiting this test to a few file systems, opt out the
> > file systems supported in common/rc that don't support overwrite
> > checking at all, and those like extN that support it, but only when
> > run interactively.
>
> If script(1) is installed, can we use it to run mkfs.extX in a sub-pty?
>
> Or is that not worth the trouble?
>
> (This is really more of a question for Ted...)
It might not be worth it. One of the reasons for it is that mkfs.ext4
can be set up to try to pull in libmagic using dlopen, to minimize the
package dependencies for things like the distribution's installer or
minimal root setu[s for Docker, et. al.
As a result, mkfs.ext4's ability a pre-existing foreign fil;e system
won't always work, depending on the libmagic shared libraery is
available. It will be a lot easier to add a test for this
functionality functionality in e2fsprogs's regression tests, since the
build system will know whether libmagic is available. So maybe it's
not worth trying to teach generic/740 how to test mkfs.ext4, at least
for now.
Cheers,
- Ted
next prev parent reply other threads:[~2024-06-25 3:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 12:10 mostly remove _supported_fs Christoph Hellwig
2024-06-23 12:10 ` [PATCH 1/8] remove support for ext4dev Christoph Hellwig
2024-06-23 12:10 ` [PATCH 2/8] generic/740: clean up handling of mkfs options Christoph Hellwig
2024-06-23 12:10 ` [PATCH 3/8] generic/740: pass the --quick option to mkfs.ntfs Christoph Hellwig
2024-06-23 12:10 ` [PATCH 4/8] generic/740: skip jffs2 as foreign fs earlier Christoph Hellwig
2024-06-23 12:10 ` [PATCH 5/8] generic/740: enable by default Christoph Hellwig
2024-06-24 16:16 ` Darrick J. Wong
2024-06-25 3:50 ` Theodore Ts'o [this message]
2024-06-25 6:00 ` Christoph Hellwig
2024-06-25 20:05 ` Theodore Ts'o
2024-06-26 4:01 ` Christoph Hellwig
2024-06-23 12:10 ` [PATCH 6/8] generic/745: rework support fs checking Christoph Hellwig
2024-06-23 12:10 ` [PATCH 7/8] generic/746: clean up fs support Christoph Hellwig
2024-06-23 12:10 ` [PATCH 8/8] remove spurious _supported_fs calls Christoph Hellwig
2024-06-24 2:17 ` mostly remove _supported_fs David Disseldorp
2024-06-24 16:17 ` Darrick J. Wong
2024-07-10 6:16 ` Christoph Hellwig
2024-07-11 13:16 ` Zorro Lang
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=20240625035008.GC7185@mit.edu \
--to=tytso@mit.edu \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-ext4@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