public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Zorro Lang <zlang@redhat.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
	"Day, Timothy" <timday@amazon.com>,
	Andreas Dilger <adilger@ddn.com>,
	Christoph Hellwig <hch@infradead.org>,
	"lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"jsimmons@infradead.org" <jsimmons@infradead.org>,
	"neilb@suse.de" <neilb@suse.de>,
	fstests <fstests@vger.kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] Lustre filesystem upstreaming
Date: Sun, 2 Feb 2025 10:26:28 -0500	[thread overview]
Message-ID: <20250202152045.GA12129@macsyma-2.local> (raw)
In-Reply-To: <20250201135911.tglbjox4dx7htrco@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>

On Sat, Feb 01, 2025 at 09:59:11PM +0800, Zorro Lang wrote:
> Thanks Amir, I think fstests has nothing to lose to support one more testing :)

Well, in the past I attempted to land a "local" file system type that
could be used for file systems that were available via docker (and so
there was no block device to mount and unmount).  This was useful for
testing gVisor[1] and could also be used for testing Windows Subsystem
for Linux v1.  As I recall, either Dave or Cristoph objected, even
though the diffstat was +73, -4 lines in common/rc.

[1] https://gvisor.dev/

So if it is really simple, it's also not hard to keep it in an
out-of-tree patch.  I've been maintaining [2] in my personal xfstests
branch, and kept it rebased on top of next, for years.  I figured it
was easier to keep it out of tree than to try to fight through Dave or
Cristoph's objects to get it upstream....

[2] https://github.com/tytso/xfstests/commit/7f8047273c8c963fdb9c3d441fe6d0f2a50cd4a3

So even if we can't get Lustre support upstream, I'm happy to maintain
it at my xfstests tree on github, much like I have with the "local"
file system type, for the past 8+ years.

Cheers,

						- Ted


  reply	other threads:[~2025-02-02 15:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 20:50 [LSF/MM/BPF TOPIC] Lustre filesystem upstreaming Day, Timothy
2025-01-24 21:09 ` Matthew Wilcox
2025-01-24 22:56   ` NeilBrown
2025-01-25  6:33   ` Day, Timothy
2025-01-28  6:14 ` Christoph Hellwig
2025-01-28 16:35   ` Day, Timothy
2025-01-30 14:28     ` Theodore Ts'o
2025-01-30 16:18       ` Day, Timothy
2025-01-30 16:56         ` Theodore Ts'o
2025-01-30 17:32           ` Day, Timothy
     [not found]       ` <4044F3FF-D0CE-4823-B104-0544A986DF7B@ddn.com>
2025-01-31 22:11         ` [Lsf-pc] " Amir Goldstein
2025-01-31 23:01           ` Day, Timothy
2025-02-01 10:55             ` Amir Goldstein
2025-02-01 13:59               ` Zorro Lang
2025-02-02 15:26                 ` Theodore Ts'o [this message]
2025-02-03  6:44                   ` Christoph Hellwig
2025-02-03 16:06                     ` Day, Timothy

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=20250202152045.GA12129@macsyma-2.local \
    --to=tytso@mit.edu \
    --cc=adilger@ddn.com \
    --cc=amir73il@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=neilb@suse.de \
    --cc=timday@amazon.com \
    --cc=zlang@redhat.com \
    /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