From: Auke Kok <auke.kok@versity.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] common: add scoutfs support.
Date: Mon, 30 Jun 2025 11:16:20 -0700 [thread overview]
Message-ID: <a9a226a0-62ca-4f50-b481-9cc4bdd04d0f@versity.com> (raw)
In-Reply-To: <aGIi7wHaq7cPMiZU@infradead.org>
On 6/29/25 10:38 PM, Christoph Hellwig wrote:
> xfstests is only really intended to test in-tree file systems, or at
> least those submitted upstream for inclusion and still in-progress.
I hear you. I don't think this will ever happen.
We've been using xfstests to test scoutfs for many years and rely
heavily on it, running it practically non-stop on scoutfs in our own CI
infrastructure, so I thought I'd at least test the waters as I'm in the
process of updating our local copy of it.
It's entirely likely we'll be maintaining scoutfs for a very long time
given our main users are deploying large scale archives with it that
have extensive lifetime spans.
Either way it's no big issue for me/us - this patch is rather small and
trivial. I do personally prefer to push things upstream once in a while
to see what feedback comes back, hence this post.
Auke
prev parent reply other threads:[~2025-06-30 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 18:42 [PATCH] common: add scoutfs support Auke Kok
2025-06-30 5:38 ` Christoph Hellwig
2025-06-30 18:16 ` Auke Kok [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=a9a226a0-62ca-4f50-b481-9cc4bdd04d0f@versity.com \
--to=auke.kok@versity.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.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