public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: viro@zeniv.linux.org.uk, brauner@kernel.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, 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 v5 00/14] ntfs filesystem remake
Date: Fri, 16 Jan 2026 10:33:48 +0100	[thread overview]
Message-ID: <20260116093348.GA22781@lst.de> (raw)
In-Reply-To: <20260111140345.3866-1-linkinjeon@kernel.org>

On Sun, Jan 11, 2026 at 11:03:30PM +0900, Namjae Jeon wrote:
>    a. Pass more xfstests tests:
>       ntfs passed 308 tests, significantly higher than ntfs3's 235.
>       ntfs passed tests are a complete superset of the tests passed
>       by ntfs3. ntfs implement fallocate, idmapped mount and permission,
>       etc, resulting in a significantly high number of xfstests passing
>       compared to ntfs3.

I'm not sure how many tests are actually run for the ntfs variants
because they lack features needed for many tests, but how many still
fail with this, because with these numbers I suspect there's quite
a few left. Do you have any good grasp why they are failing, i.e.
assumptions in xfsteasts, or missing feature checks?

Also adding this here instead of for the various patches adding the code:
there's a lot of problems with kerneldoc comments that make W=1 warns
about.  I think a lot of those are because comments are formatted as
kerneldoc when they should not.

Sparse also reports quite a lot of endianes/bitwise errors which need to
be addressed.

  parent reply	other threads:[~2026-01-16  9:34 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-11 14:03 [PATCH v5 00/14] ntfs filesystem remake Namjae Jeon
2026-01-11 14:03 ` [PATCH v5 01/14] Revert "fs: Remove NTFS classic" Namjae Jeon
2026-01-16  8:00   ` Christoph Hellwig
2026-01-11 14:03 ` [PATCH v5 02/14] ntfs: update in-memory, on-disk structures and headers Namjae Jeon
2026-01-16  8:23   ` Christoph Hellwig
2026-01-18  4:54     ` Namjae Jeon
2026-01-19  7:05       ` Christoph Hellwig
2026-01-20  4:27         ` Namjae Jeon
2026-01-20  6:40           ` Christoph Hellwig
2026-01-20  7:03             ` Namjae Jeon
2026-01-11 14:03 ` [PATCH v5 03/14] ntfs: update super block operations Namjae Jeon
2026-01-11 14:03 ` [PATCH v5 04/14] ntfs: update inode operations Namjae Jeon
2026-01-16  8:30   ` Christoph Hellwig
2026-01-18  4:54     ` Namjae Jeon
2026-01-11 14:03 ` [PATCH v5 05/14] ntfs: update directory operations Namjae Jeon
2026-01-11 14:03 ` [PATCH v5 06/14] ntfs: update file operations Namjae Jeon
2026-01-16  8:53   ` Christoph Hellwig
2026-01-18  4:56     ` Namjae Jeon
2026-01-19  7:10       ` Christoph Hellwig
2026-01-20  5:11         ` Namjae Jeon
2026-01-20  6:42           ` Christoph Hellwig
2026-01-20  7:02             ` Namjae Jeon
2026-01-11 14:03 ` [PATCH v5 07/14] ntfs: update iomap and address space operations Namjae Jeon
2026-01-16  9:14   ` Christoph Hellwig
2026-01-18  5:00     ` Namjae Jeon
2026-01-19  7:17       ` Christoph Hellwig
2026-01-20  4:28         ` Namjae Jeon
2026-01-11 14:03 ` [PATCH v5 08/14] ntfs: update attrib operations Namjae Jeon
2026-01-16  9:18   ` Christoph Hellwig
2026-01-18  5:00     ` Namjae Jeon
2026-01-11 14:03 ` [PATCH v5 09/14] ntfs: update runlist handling and cluster allocator Namjae Jeon
2026-01-16  9:21   ` Christoph Hellwig
2026-01-18  5:00     ` Namjae Jeon
2026-01-11 14:03 ` [PATCH v5 10/14] ntfs: add reparse and ea operations Namjae Jeon
2026-01-11 14:03 ` [PATCH v5 11/14] ntfs: update misc operations Namjae Jeon
2026-01-16  9:28   ` Christoph Hellwig
2026-01-18  5:00     ` Namjae Jeon
2026-01-11 14:03 ` [PATCH v5 12/14] ntfs3: remove legacy ntfs driver support Namjae Jeon
2026-01-16  9:28   ` Christoph Hellwig
2026-01-11 14:03 ` [PATCH v5 13/14] ntfs: add Kconfig and Makefile Namjae Jeon
2026-01-16  9:30   ` Christoph Hellwig
2026-01-18  5:08     ` Namjae Jeon
2026-01-19  7:19       ` Christoph Hellwig
2026-01-20  4:27         ` Namjae Jeon
2026-01-11 14:03 ` [PATCH v5 14/14] MAINTAINERS: update ntfs filesystem entry Namjae Jeon
2026-01-16  9:30   ` Christoph Hellwig
2026-01-16  9:33 ` Christoph Hellwig [this message]
2026-01-18  5:19   ` [PATCH v5 00/14] ntfs filesystem remake Namjae Jeon
2026-01-19  7:02     ` Christoph Hellwig
2026-01-20  4:26       ` 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=20260116093348.GA22781@lst.de \
    --to=hch@lst.de \
    --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=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