From: Peter Lafreniere <peter@n8pjl.ca>
To: segher@kernel.crashing.org
Cc: anton.ivanov@cambridgegreys.com, geert@linux-m68k.org,
ink@jurassic.park.msu.ru, jack@suse.cz,
johannes@sipsolutions.net, linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
linux-mips@vger.kernel.org, linux-sh@vger.kernel.org,
linux-um@lists.infradead.org, linux@armlinux.org.uk,
linuxppc-dev@lists.ozlabs.org, peter@n8pjl.ca,
reiserfs-devel@vger.kernel.org, richard.henderson@linaro.org,
richard@nod.at, tsbogend@alpha.franken.de
Subject: Re: [PATCH 0/7] arch/*: config: Remove ReiserFS from defconfig
Date: Tue, 19 Sep 2023 15:58:41 +0000 [thread overview]
Message-ID: <20230919155832.4179-1-peter@n8pjl.ca> (raw)
In-Reply-To: <20230919151630.GO19790@gate.crashing.org>
On Tue, Sep 19, 2023 at 11:16, Segher Boessenkool wrote:
>
> On Tue, Sep 19, 2023 at 12:00:34AM +0000, Peter Lafreniere wrote:
>
> > On Monday, September 18th, 2023 at 19:41, Segher Boessenkool segher@kernel.crashing.org wrote:
> >
> > > On Mon, Sep 18, 2023 at 05:56:09PM +0000, Peter Lafreniere wrote:
> > >
> > > > ReiserFS has been considered deprecated for 19 months since commit
> > > > eb103a51640e ("reiserfs: Deprecate reiserfs"). However, there are
> > > > several architectures that still build it into their defconfig kernels.
> > > >
> > > > As ReiserFS will be removed in 2025, delete all ReiserFS-related options
> > > > from defconfig files before the filesystem's removal.
> > >
> > > This is essentially equivalent to deleting the filesystem now. Why do
> > > this? Is there such a hurry?
> >
> > This is not equivalent to deleting the filesystem. The filesystem can still
> > be configured into kernels, and few distros use a defconfig kernel anyway.
>
>
> Most people who compile kernels use defconfigs though. Distros are a
> tiny minority if you look at builds.
>
> Again: why do you want this?
>
Because the filesystem is deprecated and rarely used. Those who do use ReiserFS
should migrate away from it or get ready to stop upgrading their kernels soon.
This removal from defconfig:
1) Serves as a reminder to those that use the fs that they should take the
above actions, but with the filesystem staying available should they need
it.
2) Stops building an obsolete and largely-unused filesystem unnecessarily.
Some hobbyist targets like m68k and alpha may prefer to keep all filesystems
available until total removal, but others like arm and UML have no need for
ReiserFS to be built unless specifically configured.
3) Arguably simplifies the removal of the filesystem when that takes place.
This point is admittedly quite weak.
4) Has to happen someday, unless someone steps up and volunteers to maintain
the fs. I don't find it worthwhile, but you can if you'd like. Perhaps work
towards removal will cause a user to step forward and keep their beloved
filesystem around?
5) Doesn't actually remove support for the filesystem whatsoever. I can't
emphasize this enough: users who build their own kernel and maintain a
niche filesystem like ReiserFS should know how to flip a Kconfig switch.
>
> Segher
Cheers,
Peter
next prev parent reply other threads:[~2023-09-19 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 17:56 [PATCH 0/7] arch/*: config: Remove ReiserFS from defconfig Peter Lafreniere
2023-09-18 17:57 ` [PATCH 7/7] arch: alpha: remove " Peter Lafreniere
2023-09-18 23:41 ` [PATCH 0/7] arch/*: config: Remove " Segher Boessenkool
2023-09-19 0:00 ` Peter Lafreniere
2023-09-19 15:16 ` Segher Boessenkool
2023-09-19 15:58 ` Peter Lafreniere [this message]
2023-09-19 16:02 ` Geert Uytterhoeven
2023-09-19 16:15 ` Peter Lafreniere
2023-09-20 9:30 ` Geert Uytterhoeven
2023-09-20 16:56 ` Jan Kara
2023-10-15 10:04 ` (subset) " Michael Ellerman
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=20230919155832.4179-1-peter@n8pjl.ca \
--to=peter@n8pjl.ca \
--cc=anton.ivanov@cambridgegreys.com \
--cc=geert@linux-m68k.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jack@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=richard.henderson@linaro.org \
--cc=richard@nod.at \
--cc=segher@kernel.crashing.org \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).