Linux filesystem development
 help / color / mirror / Atom feed
From: Pedro Falcato <pfalcato@suse.de>
To: Jori Koolstra <jkoolstra@xs4all.nl>,
	 "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Christian Brauner <christian@brauner.io>,
	 linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] efs: Remove EFS
Date: Fri, 19 Jun 2026 11:06:46 +0100	[thread overview]
Message-ID: <ajUSQ30oi-fyh0NH@pedro-suse.lan> (raw)
In-Reply-To: <ajUIMvi5Nyjp6t2v@lt-jori.localdomain>

On Fri, Jun 19, 2026 at 11:28:03AM +0200, Jori Koolstra wrote:
> This seems like a good idea. A couple of thoughts: should this maybe be
> CC-ed to Linus? He has in the past been critical of removing old
> filesystems. There is also something arbitrary about removing efs, but
> not minix for instance. It would be great if we had some more objective

I'm fairly sure minix is staying for the same reason alpha is staying[1]. I
don't think it's productive to unearth that particular debate at this
moment.

> criteria for removal. I have also been thinking whether there is some
> use to keep at least one old simple filesystem maintained and up to date
> with modern API. It could function as a reference.

We already have one - it's fs/ext2.
(modern API? maybe not so much. still has buffer heads, uses mpage, etc.
alas.)

[1] or that our old simple reference filesystem is ext2 and not e.g fat[2] :)
[2] i may or may not feel sick after suggesting that
-- 
Pedro

  reply	other threads:[~2026-06-19 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 21:18 [PATCH] efs: Remove EFS Matthew Wilcox (Oracle)
2026-06-19  9:28 ` Jori Koolstra
2026-06-19 10:06   ` Pedro Falcato [this message]
2026-06-19 10:19     ` Jori Koolstra
2026-06-21 21:44       ` Matthew Wilcox
2026-06-23  9:17         ` Jori Koolstra
2026-06-25 19:42 ` Darrick J. Wong

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=ajUSQ30oi-fyh0NH@pedro-suse.lan \
    --to=pfalcato@suse.de \
    --cc=christian@brauner.io \
    --cc=jkoolstra@xs4all.nl \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox