From: "Darrick J. Wong" <djwong@kernel.org>
To: Maxwell Doose <m32285159@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [RFC] Maintainership of the EFS filesystem
Date: Fri, 5 Jun 2026 21:21:12 -0700 [thread overview]
Message-ID: <20260606042112.GA6060@frogsfrogsfrogs> (raw)
In-Reply-To: <CAKqfh0GNMAnNVvTu-aydHWywR4w-+E+FBtHEV_TCXxzvh6F4uA@mail.gmail.com>
On Fri, Jun 05, 2026 at 11:02:44PM -0500, Maxwell Doose wrote:
> On Fri, Jun 5, 2026 at 10:44 PM Matthew Wilcox <willy@infradead.org> wrote:
> >
> > As I said, I don't see the point. Do you have any EFS filesystems?
>
> I don't personally have any EFS filesystems but that doesn't mean that
> others don't.
>
> > Are you volunteering to do any major development on it?
>
> Like I said, we've already found some problems, and like I said I'd
> like to fix those before it becomes a FUSE as you suggested. So I
> guess I'll volunteer to do some major development for it as well.
>
> > Why shouldn't we just delete it?
>
> Because in my eyes it's an awful practice to just delete something
> overnight (probably not your plan but still), I think we need to have
> some maintenance for some time before this gets removed.
How do you plan to do QA with the EFS driver? Is there a mkfs or fsck
program for it? I don't see one in Debian, though I didn't search that
hard.
--D
next prev parent reply other threads:[~2026-06-06 4:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 2:52 [RFC] Maintainership of the EFS filesystem Maxwell Doose
2026-06-06 3:44 ` Matthew Wilcox
2026-06-06 4:02 ` Maxwell Doose
2026-06-06 4:21 ` Al Viro
2026-06-06 4:28 ` Maxwell Doose
2026-06-06 5:17 ` Maxwell Doose
2026-06-07 22:50 ` Mateusz Guzik
2026-06-08 1:24 ` Maxwell Doose
2026-06-06 4:21 ` Darrick J. Wong [this message]
2026-06-06 4:32 ` Maxwell Doose
2026-06-07 20:57 ` Jori Koolstra
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=20260606042112.GA6060@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.