From: "Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Yangtao Li <frank.li@vivo.com>,
ethan@ethancedwards.com, asahi@lists.linux.dev,
brauner@kernel.org, dan.carpenter@linaro.org,
ernesto@corellium.com, gargaditya08@live.com,
gregkh@linuxfoundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
sven@svenpeter.dev, tytso@mit.edu, viro@zeniv.linux.org.uk,
willy@infradead.org, slava@dubeyko.com,
glaubitz@physik.fu-berlin.de
Subject: Re: Subject: [RFC PATCH v2 0/8] staging: apfs: init APFS filesystem support
Date: Wed, 21 May 2025 13:27:53 -0300 [thread overview]
Message-ID: <20250521162753.GA6112@eaf> (raw)
In-Reply-To: <n7kkoptktdvldadvymcfmnaw3yqbk6bfmzpxvgdkpsvvpc3p7i@ilqcgz7wur7i>
Hi,
just one nitpick:
On Wed, May 21, 2025 at 12:14:53PM +0200, Jan Kara wrote:
> We already carry
> quite a few filesystem drivers used by very few people and since few people
> are interested it them it's difficult to find people to get these drivers
> converted to new mount API, iomap infrastructure, new page cache APIs etc.
> which forces us to keep carring the old interfaces. This gets particularly
> painful for filesystems where we don't have full specification so usually
> the mkfs and fsck tooling is not as comprehensive which makes testing
> changes harder.
For the record, my fsck [1] is far more thorough than the official one, I
don't take data corruption lightly. It's only for testing though, it doesn't
actually fix anything. And of course it could have mistakes since the
specification is incomplete and buggy.
[1] https://github.com/linux-apfs/apfsprogs
next prev parent reply other threads:[~2025-05-21 16:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 0:13 [RFC PATCH v2 0/8] staging: apfs: init APFS filesystem support Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 1/8] staging: apfs: init lzfse compression library for APFS Ethan Carter Edwards
2025-03-20 3:00 ` Aditya Garg
2025-03-20 0:13 ` [PATCH RFC v2 2/8] staging: apfs: init unicode.{c,h} Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 3/8] staging: apfs: init apfs_raw.h to handle on-disk structures Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 4/8] staging: apfs: init libzbitmap.{c,h} for decompression Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 5/8] staging: apfs: init APFS Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 6/8] staging: apfs: init build support for APFS Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 7/8] staging: apfs: init TODO and README.rst Ethan Carter Edwards
2025-03-20 0:13 ` [PATCH RFC v2 8/8] MAINTAINERS: apfs: add entry and relevant information Ethan Carter Edwards
2025-03-20 0:43 ` [RFC PATCH v2 0/8] staging: apfs: init APFS filesystem support Gao Xiang
2025-03-20 5:39 ` Dan Carpenter
2025-05-12 10:11 ` Subject: " Yangtao Li
2025-05-12 23:40 ` Ernesto A. Fernández
2025-05-13 4:13 ` Nick Chan
2025-05-13 10:43 ` Jan Kara
2025-05-13 11:41 ` Aditya Garg
2025-05-14 20:19 ` Ernesto A. Fernández
2025-05-15 5:08 ` Nick Chan
2025-05-15 16:00 ` Sven Peter
2025-05-20 5:08 ` Yangtao Li
2025-05-20 18:59 ` Ernesto A. Fernández
2025-05-21 10:14 ` Jan Kara
2025-05-21 16:27 ` Ernesto A. Fernández [this message]
2025-05-15 5:10 ` 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=20250521162753.GA6112@eaf \
--to=ernesto.mnd.fernandez@gmail.com \
--cc=asahi@lists.linux.dev \
--cc=brauner@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=ernesto@corellium.com \
--cc=ethan@ethancedwards.com \
--cc=frank.li@vivo.com \
--cc=gargaditya08@live.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=slava@dubeyko.com \
--cc=sven@svenpeter.dev \
--cc=tytso@mit.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.