public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Xiao Yang <iceyangxiao@gmail.com>
To: Zorro Lang <zlang@redhat.com>
Cc: zlang@kernel.org, timday@amazon.com, fstests@vger.kernel.org,
	sihara@ddn.com
Subject: Re: [PATCH] fstests: Add lustre support
Date: Wed, 19 Nov 2025 15:34:24 +0900	[thread overview]
Message-ID: <61e8777f-ce11-45fc-a3f7-436c5943eee9@gmail.com> (raw)
In-Reply-To: <20251119062543.lhqaqn3h76btxyk3@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>


On 11/19/2025 3:25 PM, Zorro Lang wrote:
> Hi Yang,
> 
> As you can see, the fstests community doesn't like to spend time on
> maintaining fstests for out-of-tree fs, especially downstream-only filesystems.
> I'm not a dictator. If we accept to support someone filesystem and its
> patches, that means we'd like to spend time to review patches for it, think
> about it when update fstests, fix issues on it, and so on. So I'd like to
> respect the willing of fstests community.
> 
> For bcachefs, it was in-tree, and we know its contributors are still trying to
> keep it up to date. So I'd like to keep its supporting.
> 
> For glusterfs, it's an upstream open-source filesystem, it's base on FUSE of linux
> kernel. It can't be a kernel module, but it's a pure upstream fs at least. Actually
> I brought in it for testing FUSE at beginning.
> 
> So do you do this for*upstreaming* the lustre filesystem (any active source code link?)
> or just for using xfstests downstream? If it's the latter, I'd suggest you to fork
> xfstests, and maintain this patch downstream.
> 
> I noticed that there was a discussion about Lustre filesystem upstreaming:
> https://lore.kernel.org/linux-fsdevel/DA28F0FE-ACB6-486E-BF3D-85AF328FE2AD@amazon.com/T/#med943c38d27ddac1b68e9db37d6b0f2803ee6133
> 
> But I haven't found it's online. So if the "lustre upstreaming" project get
> an offical version be acked by mainline linux, fstests willing to support
> its later developing/testing. At your early developing stage, I think you
> can fork and maintain a downstream xfstests temporarily.
> 
> Thanks,
> Zorro

Hi zorro

Thanks for your explanation.
OK, I will fork xfstests and maintain it downstream for now.

Best Regards,
Xiao Yang


      reply	other threads:[~2025-11-19  6:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18  7:30 [PATCH] fstests: Add lustre support Xiao Yang
2025-11-18 12:50 ` Christoph Hellwig
2025-11-18 15:23   ` Day, Timothy
2025-11-19  4:10     ` Xiao Yang
2025-11-19  6:15     ` Christoph Hellwig
2025-11-18 14:52 ` Day, Timothy
2025-11-19  4:32   ` Xiao Yang
2025-11-19  6:25 ` Zorro Lang
2025-11-19  6:34   ` Xiao Yang [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=61e8777f-ce11-45fc-a3f7-436c5943eee9@gmail.com \
    --to=iceyangxiao@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=sihara@ddn.com \
    --cc=timday@amazon.com \
    --cc=zlang@kernel.org \
    --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