From: Matthew Wilcox <willy@infradead.org>
To: Maxwell Doose <m32285159@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Fabian Frederick <fabf@skynet.be>,
open list <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: efs: Fix compilation bug and use pr_debug()
Date: Fri, 5 Jun 2026 17:59:29 +0100 [thread overview]
Message-ID: <aiMAcSooHzy0TMCN@casper.infradead.org> (raw)
In-Reply-To: <CAKqfh0FFB0EkTAh-+6uK0aNqWVZhdwMpP5-Nnz4GEoWYXQM3Dw@mail.gmail.com>
On Thu, Jun 04, 2026 at 10:33:10PM -0500, Maxwell Doose wrote:
> On Thu, Jun 4, 2026 at 10:27 PM Matthew Wilcox <willy@infradead.org> wrote:
> >
> > On Thu, Jun 04, 2026 at 10:16:44PM -0500, Maxwell Doose wrote:
> > > ps: I noticed this was listed as an orphan in MAINTAINERS. I'd be
> > > happy to step up and maintain this, I've got a bit of experience
> > > maintaining stuff in iio. Hopefully this isn't too far-fetched!
> >
> > I'd be just as happy to see it deleted. efs was succeeded by XFS in
> > the mid-90s. The last efs filesystem I personally saw was in 1999 (an
> > SGI Freeware CD). If there's any filesystem crying out to be converted
> > to FUSE and removed from the kernel, this is it.
>
> I guess that is a fair point. But given the fact that we quite
> literally just found a compile-time bug I think there may be further
> underlying issues that need to be resolved before conversion to FUSE
> :/
I'd argue that shows the exact opposite. efs just isn't useful any more.
While looking up some information on Wikipedia, I discovered that XFS
filesystems from SGI used v2 of the directory format. Linux no longer
supports anything from before v4 (and even that is now under a CONFIG
option). So we're in the weird situation where SGI filesystems from
1992 are readable in Linux, but SGI filesystems from 1995 are not.
prev parent reply other threads:[~2026-06-05 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 20:24 Maxwell Doose
2026-06-04 21:30 ` Andrew Morton
2026-06-05 1:40 ` Maxwell Doose
2026-06-05 2:53 ` Andrew Morton
2026-06-05 3:16 ` Maxwell Doose
2026-06-05 3:27 ` Matthew Wilcox
2026-06-05 3:33 ` Maxwell Doose
2026-06-05 16:59 ` Matthew Wilcox [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=aiMAcSooHzy0TMCN@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.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
all inboxes | Powered by JetHome®