From: "Pali Rohár" <pali@kernel.org>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: viro@zeniv.linux.org.uk, brauner@kernel.org, hch@infradead.org,
hch@lst.de, tytso@mit.edu, willy@infradead.org, jack@suse.cz,
djwong@kernel.org, josef@toxicpanda.com, sandeen@sandeen.net,
rgoldwyn@suse.com, xiang@kernel.org, dsterba@suse.com,
ebiggers@kernel.org, neil@brown.name, amir73il@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
iamjoonsoo.kim@lge.com, cheol.lee@lge.com, jay.sim@lge.com,
gunho.lee@lge.com
Subject: Re: [PATCH 00/11] ntfsplus: ntfs filesystem remake
Date: Mon, 20 Oct 2025 20:33:04 +0200 [thread overview]
Message-ID: <20251020183304.umtx46whqu4awijj@pali> (raw)
In-Reply-To: <20251020020749.5522-1-linkinjeon@kernel.org>
Hello,
Do you have a plan, what should be the future of the NTFS support in
Linux? Because basically this is a third NTFS driver in recent years
and I think it is not a good idea to replace NTFS driver every decade by
a new different implementation.
Is this new driver going to replace existing ntfs3 driver? Or should it
live side-by-side together with ntfs3?
If this new driver is going to replace ntfs3 then it should provide same
API/ABI to userspace. For this case at least same/compatible mount
options, ioctl interface and/or attribute features (not sure what is
already supported).
You wrote that ntfsplus is based on the old ntfs driver. How big is the
diff between old ntfs and new ntfsplus driver? If the code is still
same, maybe it would be better to call it ntfs as before and construct
commits in a way which will first "revert the old ntfs driver" and then
apply your changes on top of it (like write feature, etc..)?
For mount options, for example I see that new driver does not use
de-facto standard iocharset= mount option like all other fs driver but
instead has nls= mount option. This should be fixed.
Pali
next prev parent reply other threads:[~2025-10-20 18:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 2:07 [PATCH 00/11] ntfsplus: ntfs filesystem remake Namjae Jeon
2025-10-20 2:07 ` [PATCH 01/11] ntfsplus: in-memory, on-disk structures and headers Namjae Jeon
2025-10-20 2:07 ` [PATCH 02/11] ntfsplus: add super block operations Namjae Jeon
2025-10-20 2:07 ` [PATCH 03/11] ntfsplus: add inode operations Namjae Jeon
2025-10-20 2:07 ` [PATCH 04/11] ntfsplus: add directory operations Namjae Jeon
2025-10-20 2:07 ` [PATCH 05/11] ntfsplus: add file operations Namjae Jeon
2025-10-20 18:33 ` Pali Rohár [this message]
2025-10-21 1:49 ` [PATCH 00/11] ntfsplus: ntfs filesystem remake Namjae Jeon
2025-10-21 22:19 ` Pali Rohár
2025-10-22 2:13 ` Namjae Jeon
2025-10-22 18:52 ` Pali Rohár
2025-10-22 22:32 ` Namjae Jeon
2025-10-21 0:17 ` Bagas Sanjaya
2025-10-21 1:55 ` Namjae Jeon
2025-10-26 5:37 ` Bagas Sanjaya
2025-10-22 6:30 ` David Sterba
2025-10-22 8:33 ` Namjae Jeon
2025-10-22 18:57 ` Pali Rohár
-- strict thread matches above, loose matches on Subject: below --
2025-10-22 21:24 Lassebq
[not found] <7YXJ4T.2LNCI9JPXKCZ2@gmail.com>
2025-10-23 7:20 ` Namjae Jeon
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=20251020183304.umtx46whqu4awijj@pali \
--to=pali@kernel.org \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=cheol.lee@lge.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=ebiggers@kernel.org \
--cc=gunho.lee@lge.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=iamjoonsoo.kim@lge.com \
--cc=jack@suse.cz \
--cc=jay.sim@lge.com \
--cc=josef@toxicpanda.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
--cc=rgoldwyn@suse.com \
--cc=sandeen@sandeen.net \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=xiang@kernel.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).