From: "Sven Peter" <sven@svenpeter.dev>
To: "Ethan Carter Edwards" <ethan@ethancedwards.com>,
linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-staging@lists.linux.dev,
asahi@lists.linux.dev
Subject: Re: [RFC] apfs: thoughts on upstreaming an out-of-tree module
Date: Sat, 01 Mar 2025 00:04:27 +0100 [thread overview]
Message-ID: <d0be518b-3abf-497a-b342-ff862dd985a7@app.fastmail.com> (raw)
In-Reply-To: <rxefeexzo2lol3qph7xo5tgnykp5c6wcepqewrze6cqfk22leu@wwkiu7yzkpvp>
Hi,
On Fri, Feb 28, 2025, at 02:53, Ethan Carter Edwards wrote:
> Lately, I have been thinking a lot about the lack of APFS support on
> Linux. I was wondering what I could do about that. APFS support is not
> in-tree, but there is a proprietary module sold by Paragon software [0].
> Obviously, this could not be used in-tree. However, there is also an
> open source driver that, from what I can tell, was once planned to be
> upstreamed [1] with associated filesystem progs [2]. I think I would
> base most of my work off of the existing FOSS tree.
>
> The biggest barrier I see currently is the driver's use of bufferheads.
> I realize that there has been a lot of work to move existing filesystem
> implementations to iomap/folios, and adding a filesystem that uses
> bufferheads would be antithetical to the purpose of that effort.
> Additionally, there is a lot of ifndefs/C preprocessor magic littered
> throughout the codebase that fixes functionality with various different
> versions of Linux.
>
> The first step would be to move away from bufferheads and the
> versioning. I plan to start my work in the next few weeks, and hope to
> have a working driver to submit to staging by the end of June. From
> there, I will work to have it meet more kernel standards and hopefully
> move into fs/ by the end of the year.
>
> Before I started, I was wondering if anyone had any thoughts. I am open
> to feedback. If you think this is a bad idea, let me know. I am very
> passionate about the Asahi Linux project. I think this would be a good
> way to indirectly give back and contribute to the project. While I
> recognize that it is not one of Asahi's project goals (those being
> mostly hardware support), I am confident many users would find it
> helpful. I sure would.
Agreed, I think it would be helpful for many people (especially those
who still regularly dual boot between macOS and Linux) to have a working
APFS driver upstream.
This may also be useful once we fully bring up the Secure Enclave and need
to read/write to at least a single file on the xART partition which has
to be APFS because it's shared between all operating systems running on
a single machine.
It looks like there's still recent activity on that linux-apfs github
repository. Have you reached out to the people working on it to see
what their plans for upstreaming and/or future work are?
Best,
Sven
next prev parent reply other threads:[~2025-02-28 23:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 1:53 [RFC] apfs: thoughts on upstreaming an out-of-tree module Ethan Carter Edwards
2025-02-28 12:55 ` Theodore Ts'o
2025-03-01 16:26 ` Ethan Carter Edwards
2025-02-28 23:04 ` Sven Peter [this message]
2025-03-01 16:39 ` Ethan Carter Edwards
2025-03-05 7:23 ` Aditya Garg
2025-03-06 18:04 ` Theodore Ts'o
2025-03-06 19:39 ` Sven Peter
2025-03-07 16:50 ` Ernesto A. Fernández
2025-03-02 10:55 ` Dan Carpenter
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=d0be518b-3abf-497a-b342-ff862dd985a7@app.fastmail.com \
--to=sven@svenpeter.dev \
--cc=asahi@lists.linux.dev \
--cc=ethan@ethancedwards.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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