FS/XFS testing framework
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Christian Brauner <brauner@kernel.org>
Cc: Eryu Guan <guaneryu@gmail.com>,
	Seth Forshee <sforshee@digitalocean.com>,
	Christoph Hellwig <hch@lst.de>, Peter Jin <peter@peterjin.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	fstests@vger.kernel.org, Amir Goldstein <amir73il@gmail.com>
Subject: Re: [PATCH] generic: add test for tmpfs POSIX ACLs
Date: Thu, 21 Apr 2022 09:18:31 +0200	[thread overview]
Message-ID: <20220421071831.GA24199@lst.de> (raw)
In-Reply-To: <20220421070513.wcqz7kzmcm3u5uok@wittgenstein>

On Thu, Apr 21, 2022 at 09:05:13AM +0200, Christian Brauner wrote:
> I'd like to avoid that. The testsuite tests a lot of core vfs
> functionality - completely indepenent of idmapped mounts which is why I
> should rename it - that isn't covered anwywhere else in xfstests.
> It also contains various regressions tests for core vfs work.
> Let's keep it in a single repo which will guarantee us that it will be
> run as part of xfstests.

Yeah, that unionmount testsuite is something no casual users will
run as it requires way too much effort to be usable.

  reply	other threads:[~2022-04-21  7:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220419131423.2367795-1-brauner@kernel.org>
2022-04-20 17:52 ` [PATCH] generic: add test for tmpfs POSIX ACLs Christian Brauner
2022-04-21  5:41   ` Zorro Lang
2022-04-21  7:05     ` Christian Brauner
2022-04-21  7:18       ` Christoph Hellwig [this message]
2022-04-21  7:52         ` Amir Goldstein
2022-04-21  7:55           ` Christoph Hellwig
2022-04-21  8:59     ` Dave Chinner
2022-04-21 15:35       ` Zorro Lang
2022-04-21 15:37         ` Christoph Hellwig
2022-04-21 15:53           ` Christian Brauner
2022-04-23  7:17             ` Amir Goldstein
2022-04-23 11:07               ` Christian Brauner

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=20220421071831.GA24199@lst.de \
    --to=hch@lst.de \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=guaneryu@gmail.com \
    --cc=peter@peterjin.org \
    --cc=sforshee@digitalocean.com \
    --cc=torvalds@linux-foundation.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