From: Namjae Jeon <linkinjeon@kernel.org>
To: Anton Altaparmakov <anton@tuxera.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net, ntfs3@lists.linux.dev
Subject: Re: [PATCH] fs: Remove NTFS classic
Date: Mon, 15 Jan 2024 20:41:42 +0900 [thread overview]
Message-ID: <CAKYAXd9VcORULpRUGpBYpZKc=GTV4vOAvv-B-rVVxfbz-y1TOQ@mail.gmail.com> (raw)
In-Reply-To: <8a5d4fcb-f6dc-4c7e-a26c-0b0e91430104@tuxera.com>
2024-01-15 20:00 GMT+09:00, Anton Altaparmakov <anton@tuxera.com>:
> Hi Matthew,
>
> On 15/01/2024 07:20, Matthew Wilcox (Oracle) wrote:
>> The replacement, NTFS3, was merged over two years ago. It is now time to
>> remove the original from the tree as it is the last user of several APIs,
>> and it is not worth changing.
>
> It was my impression that people are complaining ntfs3 is causing a
> whole lot of problems including corrupting people's data. Also, it
> appears the maintainer has basically disappeared after it got merged.
What can replace this is not only ntfs3 but also ntfs3g. I think
read-only ntfs is obsolete.
I am in favor of remove it.
Acked-by: Namjae Jeon <linkinjeon@kernel.org>
Thanks.
>
> Is it really such a good idea to remove the original ntfs driver which
> actually works fine and does not cause any problems when the replacement
> is so poor and unmaintained?
>
> Also, which APIs are you referring to? I can take a look into those.
>
> Best regards,
>
> Anton
> --
> Anton Altaparmakov <anton at tuxera.com> (replace at with @)
> Lead in File System Development, Tuxera Inc., http://www.tuxera.com/
> Linux NTFS maintainer
>
next prev parent reply other threads:[~2024-01-15 11:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 7:20 [PATCH] fs: Remove NTFS classic Matthew Wilcox (Oracle)
2024-01-15 11:00 ` Anton Altaparmakov
2024-01-15 11:08 ` Enrico Mioso
2024-01-15 11:41 ` Namjae Jeon [this message]
2024-01-15 14:49 ` Matthew Wilcox
2024-01-16 9:52 ` [PATCH] " Anton Altaparmakov
2024-01-15 22:20 ` [PATCH] fs: " Dave Chinner
2024-01-16 9:33 ` Christian Brauner
2024-01-16 9:51 ` [PATCH] " Anton Altaparmakov
2024-01-16 11:06 ` Christian Brauner
2024-01-16 11:32 ` Anton Altaparmakov
2024-03-22 16:35 ` [PATCH] fs: " Johan Hovold
2024-03-25 8:28 ` Christian Brauner
2024-03-25 8:34 ` [PATCH 1/2] ntfs3: serve as alias for the legacy ntfs driver Christian Brauner
2024-03-25 10:09 ` Johan Hovold
2024-03-25 12:01 ` Christian Brauner
2024-03-25 8:34 ` [PATCH 2/2] ntfs3: remove warning Christian Brauner
2024-03-25 10:12 ` Johan Hovold
2024-03-25 12:05 ` Christian Brauner
2024-04-04 8:06 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-11 11:03 ` Konstantin Komarov
2024-04-15 9:54 ` Johan Hovold
2024-04-15 10:20 ` Johan Hovold
2024-04-15 11:32 ` Anton Altaparmakov
2024-04-15 11:42 ` Johan Hovold
2024-04-15 14:15 ` Christian Brauner
2024-04-15 15:23 ` Linus Torvalds
2024-04-15 15:27 ` Matthew Wilcox
2024-04-15 15:47 ` Johan Hovold
2024-04-15 15:51 ` Linus Torvalds
2024-04-15 16:06 ` Johan Hovold
2024-04-16 10:38 ` Christian Brauner
2024-04-16 12:55 ` Johan Hovold
2024-04-17 16:07 ` Konstantin Komarov
2024-04-18 6:36 ` Johan Hovold
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='CAKYAXd9VcORULpRUGpBYpZKc=GTV4vOAvv-B-rVVxfbz-y1TOQ@mail.gmail.com' \
--to=linkinjeon@kernel.org \
--cc=anton@tuxera.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=ntfs3@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).