All of
 help / color / mirror / Atom feed
From: Kari Argillander <>
To: Theodore Ts'o <>
Cc: Kari Argillander <>,
Subject: Re: [xfstests-bld PATCH 0/2] Make ntfs3 more usable
Date: Fri, 15 Apr 2022 11:27:38 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 15.4.2022 7.22, Theodore Ts'o wrote:
> On Fri, Apr 15, 2022 at 02:42:18AM +0300, Kari Argillander wrote:
>> Add ntfs3 kernel configs and disable tests which hangs at the moment.
>> Kari Argillander (2):
>>    test-appliance: Add exclude file for ntfs3
>>    kernel-configs: add ntfs3 to current 5.15 configs
> Note that upstream fstests does *not* have support for ntfs3 at the
> moment.  I have some admittedly very hacky patches in my personal fork
> of xfstests on github, but they use a mix of userspace tools that are
> specific for other ntfs file system drivers, since last I checked,
> Paragon software has not made open source file system utilities for
> ntfs3 available.

Yes I'm fully aware of situation. I just try to make situation little 
bit better and have to start somewhere. Hopefully someone other will 
also start gain interest developing this if tools are easier to use.

> The support of ntfs3 in {kvm,gce}-xfstests was experimental in nature
> when I was trying to make an assessment about whether ntfs3 was ready
> for prime time.  So don't mind applying these patches, but I'm
> currently no longer regularly running ntfs3 test runs, and I'm very
> much aware that the current ntfs3 support that I had added a while
> back into xfstests is definitely not polished or ready for the fstests
> maintainer to consider accepting.
I also planning to do better Xfstests support for ntfs3. Your tool at 
the moment is still only way testing it for new developers so I just 
want it to be little bit easier. I do not except you to run ntfs3. I 
also know about your previes patch. I will polish that to be usable.

I have also made ntfs3 support for Syzkaller and my patch will probably 
be merged this week. It means next week there will probably start coming 
some bug reports from there too. Local Syzkaller run against ntfs3 does 
not see very promising and there will be some bugs. But hey testing 
helps as we see how buggy things are.

Thing is that Konstantin (ntfs3 maintainer) has kept totally radio 
silence after 5.15 was released. I will make own thread about it soon as 
ntfs3 is orphan already. But that will need definitely own thread.


> Cheers,
> 					- Ted

      reply	other threads:[~2022-04-15  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 23:42 [xfstests-bld PATCH 0/2] Make ntfs3 more usable Kari Argillander
2022-04-14 23:42 ` [xfstests-bld PATCH 1/2] test-appliance: Add exclude file for ntfs3 Kari Argillander
2022-04-15  1:39   ` Darrick J. Wong
2022-04-14 23:42 ` [xfstests-bld PATCH 2/2] kernel-configs: add ntfs3 to current 5.15 configs Kari Argillander
2022-04-15  4:22 ` [xfstests-bld PATCH 0/2] Make ntfs3 more usable Theodore Ts'o
2022-04-15  8:27   ` Kari Argillander [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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.