From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Namjae Jeon <linkinjeon@kernel.org>,
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,
pali@kernel.org, ebiggers@kernel.org, neil@brown.name,
amir73il@gmail.com
Cc: 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: Tue, 21 Oct 2025 07:17:45 +0700 [thread overview]
Message-ID: <aPbRKScRgkxUDYew@archie.me> (raw)
In-Reply-To: <20251020020749.5522-1-linkinjeon@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On Mon, Oct 20, 2025 at 11:07:38AM +0900, Namjae Jeon wrote:
> Introduction
> ============
Can you write the documentation at least in
Documentation/filesystems/ntfsplus.rst?
> - Journaling support:
> ntfs3 does not provide full journaling support. It only implement journal
> replay[4], which in our testing did not function correctly. My next task
> after upstreaming will be to add full journal support to ntfsplus.
What's the plan for journaling? Mirroring the Windows implementation AFAIK?
For the timeline: I guess you plan to submit journaling patches right after
ntfsplus is merged (at least applied to the filesystem tree or direct PR to
Linus), or would it be done for the subsequent release cycle (6.n+1)?
Regarding stability: As it is a new filesystem, shouldn't it be marked
experimental (and be stabilized for a few cycles) first?
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-21 0:17 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 ` [PATCH 00/11] ntfsplus: ntfs filesystem remake Pali Rohár
2025-10-21 1:49 ` 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 [this message]
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=aPbRKScRgkxUDYew@archie.me \
--to=bagasdotme@gmail.com \
--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=pali@kernel.org \
--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).