From: "Darrick J. Wong" <djwong@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
David Sterba <dsterba@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Josef Bacik <josef@toxicpanda.com>, Sandeen <sandeen@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hfs{plus}: add deprecation warning
Date: Wed, 16 Apr 2025 08:06:04 -0700 [thread overview]
Message-ID: <20250416150604.GB25700@frogsfrogsfrogs> (raw)
In-Reply-To: <20250416-willen-wachhalten-55a798e41fd2@brauner>
On Wed, Apr 16, 2025 at 08:27:19AM +0200, Christian Brauner wrote:
> On Tue, Apr 15, 2025 at 07:49:07AM -0700, Darrick J. Wong wrote:
> > On Tue, Apr 15, 2025 at 09:51:37AM +0200, Christian Brauner wrote:
> > > Both the hfs and hfsplus filesystem have been orphaned since at least
> > > 2014, i.e., over 10 years. It's time to remove them from the kernel as
> > > they're exhibiting more and more issues and no one is stepping up to
> > > fixing them.
> > >
> > > Signed-off-by: Christian Brauner <brauner@kernel.org>
> > > ---
> > > fs/hfs/super.c | 2 ++
> > > fs/hfsplus/super.c | 2 ++
> > > 2 files changed, 4 insertions(+)
> > >
> > > diff --git a/fs/hfs/super.c b/fs/hfs/super.c
> > > index fe09c2093a93..4413cd8feb9e 100644
> > > --- a/fs/hfs/super.c
> > > +++ b/fs/hfs/super.c
> > > @@ -404,6 +404,8 @@ static int hfs_init_fs_context(struct fs_context *fc)
> > > {
> > > struct hfs_sb_info *hsb;
> > >
> > > + pr_warn("The hfs filesystem is deprecated and scheduled to be removed from the kernel in 2025\n");
> >
> > Does this mean before or after the 2025 LTS kernel is released? I would
>
> I would've tried before the LTS release...
Well you still could. No better way to get an oft-ignored filesystem
back into maintenance by throwing down a deprecation notice. :)
> > say that we ought to let this circulate more widely among users, but
>
> which is a valid point. The removal of reiserfs and sysv has been pretty
> surgically clean. So at least from my POV it should be simple enough to
> revert the removal. But I'm not dealing with stable kernels so I have no
> intuition about the pain involved.
It'll probably cause a lot of pain for the distributions that support
PPC Macs because that's the only fs that the OF knows how to read for
bootfiles. For dual-boot Intel Macs, their EFI partition is usually
HFS+ and contains various system files (+ grub), but their EFI actually
can read FAT. I have an old 2012 Mac Mini that runs exclusively Debian,
and a FAT32 ESP works just fine.
> > OTOH I guess no maintainer for a decade is really bad.
On those grounds,
Acked-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> >
> > --D
> >
> > > +
> > > hsb = kzalloc(sizeof(struct hfs_sb_info), GFP_KERNEL);
> > > if (!hsb)
> > > return -ENOMEM;
> > > diff --git a/fs/hfsplus/super.c b/fs/hfsplus/super.c
> > > index 948b8aaee33e..58cff4b2a3b4 100644
> > > --- a/fs/hfsplus/super.c
> > > +++ b/fs/hfsplus/super.c
> > > @@ -656,6 +656,8 @@ static int hfsplus_init_fs_context(struct fs_context *fc)
> > > {
> > > struct hfsplus_sb_info *sbi;
> > >
> > > + pr_warn("The hfsplus filesystem is deprecated and scheduled to be removed from the kernel in 2025\n");
> > > +
> > > sbi = kzalloc(sizeof(struct hfsplus_sb_info), GFP_KERNEL);
> > > if (!sbi)
> > > return -ENOMEM;
> > > --
> > > 2.47.2
> > >
> > >
next prev parent reply other threads:[~2025-04-16 15:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 7:51 [PATCH] hfs{plus}: add deprecation warning Christian Brauner
2025-04-15 10:08 ` Jan Kara
2025-04-15 14:49 ` Darrick J. Wong
2025-04-16 6:27 ` Christian Brauner
2025-04-16 15:06 ` Darrick J. Wong [this message]
2025-04-16 17:56 ` Viacheslav Dubeyko
2025-04-17 9:29 ` John Paul Adrian Glaubitz
2025-04-17 18:10 ` Viacheslav Dubeyko
2025-04-17 18:14 ` John Paul Adrian Glaubitz
2025-04-17 21:44 ` Viacheslav Dubeyko
2025-04-23 4:24 ` Yangtao Li
2025-04-23 4:38 ` Viacheslav Dubeyko
2025-04-23 6:52 ` John Paul Adrian Glaubitz
2025-04-17 8:59 ` John Paul Adrian Glaubitz
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=20250416150604.GB25700@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=dsterba@suse.cz \
--cc=jack@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox