From: Christoph Hellwig <hch@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Zorro Lang <zlang@redhat.com>,
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 22:44:20 -0800 [thread overview]
Message-ID: <Z6BlxO4YjsjPQyuY@infradead.org> (raw)
In-Reply-To: <20250202152045.GA12129@macsyma-2.local>
On Sun, Feb 02, 2025 at 10:26:28AM -0500, Theodore Ts'o wrote:
> 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.
Yes, xfstests should just support upstream code. Even for things where
we through it would get upstream ASAP like the XFS
rtrmap/reflink/metadir work (which finally did get upstream now) having
the half-finished support in xfstests without actually landing the rest
caused more than enough problems. Something like lustre that has
historically been a complete trainwreck and where I have strong doubts
that the maintainers get their act together is even worse.
next prev parent reply other threads:[~2025-02-03 6:44 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
2025-02-03 6:44 ` Christoph Hellwig [this message]
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=Z6BlxO4YjsjPQyuY@infradead.org \
--to=hch@infradead.org \
--cc=adilger@ddn.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.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=tytso@mit.edu \
--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