Re: [PATCH v11 00/10] NTFS read-write driver GPL implementation by Paragon Software

From: Pali Rohár
Date: Fri Oct 30 2020 - 12:41:28 EST


Hello!

On Friday 30 October 2020 18:02:29 Konstantin Komarov wrote:
> 27 files changed, 28364 insertions(+)
> create mode 100644 Documentation/filesystems/ntfs3.rst
> create mode 100644 fs/ntfs3/Kconfig
> create mode 100644 fs/ntfs3/Makefile
> create mode 100644 fs/ntfs3/attrib.c
> create mode 100644 fs/ntfs3/attrlist.c
> create mode 100644 fs/ntfs3/bitfunc.c
> create mode 100644 fs/ntfs3/bitmap.c
> create mode 100644 fs/ntfs3/debug.h
> create mode 100644 fs/ntfs3/dir.c
> create mode 100644 fs/ntfs3/file.c
> create mode 100644 fs/ntfs3/frecord.c
> create mode 100644 fs/ntfs3/fslog.c
> create mode 100644 fs/ntfs3/fsntfs.c
> create mode 100644 fs/ntfs3/index.c
> create mode 100644 fs/ntfs3/inode.c
> create mode 100644 fs/ntfs3/lznt.c
> create mode 100644 fs/ntfs3/namei.c
> create mode 100644 fs/ntfs3/ntfs.h
> create mode 100644 fs/ntfs3/ntfs_fs.h
> create mode 100644 fs/ntfs3/record.c
> create mode 100644 fs/ntfs3/run.c
> create mode 100644 fs/ntfs3/super.c
> create mode 100644 fs/ntfs3/upcase.c
> create mode 100644 fs/ntfs3/xattr.c

I would like to open discussion about two ntfs kernel drivers. Do we
really need two drivers (one read only - current version and one
read/write - this new version)?

What other people think?

I remember that Christoph (added to loop) had in past a good argument
about old staging exfat driver (it had support also for fat32/vfat),
that it would cause problems if two filesystem drivers would provide
support for same filesystem.