From: "Theodore Ts'o" <tytso@mit.edu>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: Christoph Hellwig <hch@lst.de>, Eryu Guan <guan@eryu.me>,
Christian Brauner <brauner@kernel.org>,
fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
"Darrick J . Wong" <djwong@kernel.org>,
David Howells <dhowells@redhat.com>,
Amir Goldstein <amir73il@gmail.com>
Subject: Re: [PATCH -RFC] ext4: add feature file to advertise that ext4 supports idmapped mounts
Date: Thu, 15 Apr 2021 10:59:28 -0400 [thread overview]
Message-ID: <YHhU0MGFgiXMRrBn@mit.edu> (raw)
In-Reply-To: <20210415074921.cf5uv4xehlctvtvv@wittgenstein>
On Thu, Apr 15, 2021 at 09:49:21AM +0200, Christian Brauner wrote:
> Harsh words. :)
> Christoph's right though I think for the xfstests we don't need it and
> we're covered with what we have in the version I sent out last Sunday.
Sorry, I had missed your v13 patch set and that it had included tests
for the existence of idmapped. I had sent out the RFC patch because I
was under the impression that we hadn't made forward progress on
testing for the support idmapped mounts.
If we have a way of doing this, and you're comfortable that it is
reliable (e.g., that a bug might cause the test to be skipped because
it thinks the file system doesn't support idmapped mount, when really
it was caused by a regression), and I'm happy to just rely on the
method you've used in the v13 fstests patch set.
That being said, I still think it would be helpful to have a
VFS-standard way for userspace to be able to test for the presence of
a particular kernel feature/capability without having to do a test
mount, possibly requiring setting up a test user_ns, etc., etc. But
that isn't as urgent as making sure we can easily the feature without
needing manual customization of the test suite as file systems add
support for the feature, or as the feature gets backported to
enterprise distro kernels.
Cheers,
- Ted
prev parent reply other threads:[~2021-04-15 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210328223400.1800301-1-brauner@kernel.org>
[not found] ` <20210328223400.1800301-3-brauner@kernel.org>
[not found] ` <YHMH/JRmzg3ETcED@desktop>
[not found] ` <20210411151249.6y34x7yatqtpcvi6@wittgenstein>
[not found] ` <20210411151857.wd6gd46u53vlh2xv@wittgenstein>
[not found] ` <YHMUAL/oD4fB3+R7@desktop>
[not found] ` <20210411153223.vhcegiklrwoczy55@wittgenstein>
[not found] ` <YHOW7DN51YuYgLPM@mit.edu>
[not found] ` <20210412115426.a4bzsx4cp7jhx2ou@wittgenstein>
[not found] ` <YHTMkBcVTFAGqyks@mit.edu>
2021-04-14 20:47 ` [PATCH -RFC] ext4: add feature file to advertise that ext4 supports idmapped mounts Theodore Ts'o
2021-04-15 5:54 ` Christoph Hellwig
2021-04-15 7:49 ` Christian Brauner
2021-04-15 7:55 ` Christoph Hellwig
2021-04-15 8:13 ` Christian Brauner
2021-04-15 14:59 ` 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=YHhU0MGFgiXMRrBn@mit.edu \
--to=tytso@mit.edu \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=dhowells@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=hch@lst.de \
--cc=linux-ext4@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