From: "Pali Rohár" <pali@kernel.org>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org, dsterba@suse.cz, aaptel@suse.com,
willy@infradead.org, rdunlap@infradead.org, joe@perches.com,
mark@harmstone.com, nborisov@suse.com,
linux-ntfs-dev@lists.sourceforge.net, anton@tuxera.com,
dan.carpenter@oracle.com, hch@lst.de, ebiggers@kernel.org,
andy.lavr@gmail.com, kari.argillander@gmail.com,
oleksandr@natalenko.name
Subject: Re: [PATCH v26 00/10] NTFS read-write driver GPL implementation by Paragon Software
Date: Sat, 17 Jul 2021 18:36:18 +0200 [thread overview]
Message-ID: <20210717163618.vt6zjnhaiey6l64m@pali> (raw)
In-Reply-To: <20210402155347.64594-1-almaz.alexandrovich@paragon-software.com>
Hello!
I would like to remind that there are still two open questions about
this ntfs driver which needs to be resolved by vfs maintainers (Al?)
prior merging / accepting this driver into kernel tree.
1) Should this new ntfs driver use and implement old FAT ioctl calls?
These ioctls are added in patch: Add file operations and implementation.
First time I wrote about them in email:
https://lore.kernel.org/linux-fsdevel/20200921133647.3tczqm5zfvae6q6a@pali/
2) Should kernel have two ntfs drivers? And if yes, how they would
interact to userspace? Both Christoph and me think that not, see email:
https://lore.kernel.org/linux-fsdevel/20201031085142.GA5949@lst.de/
next prev parent reply other threads:[~2021-07-17 16:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 15:53 [PATCH v26 00/10] NTFS read-write driver GPL implementation by Paragon Software Konstantin Komarov
2021-04-02 15:53 ` [PATCH v26 01/10] fs/ntfs3: Add headers and misc files Konstantin Komarov
2021-04-02 15:53 ` [PATCH v26 02/10] fs/ntfs3: Add initialization of super block Konstantin Komarov
2021-05-20 16:51 ` Darrick J. Wong
2021-04-02 15:53 ` [PATCH v26 03/10] fs/ntfs3: Add bitmap Konstantin Komarov
2021-04-02 15:53 ` [PATCH v26 04/10] fs/ntfs3: Add file operations and implementation Konstantin Komarov
2021-07-12 8:28 ` Oleksandr Natalenko
2021-04-02 15:53 ` [PATCH v26 05/10] fs/ntfs3: Add attrib operations Konstantin Komarov
2021-04-02 15:53 ` [PATCH v26 06/10] fs/ntfs3: Add compression Konstantin Komarov
2021-04-02 15:53 ` [PATCH v26 07/10] fs/ntfs3: Add NTFS journal Konstantin Komarov
2021-04-02 15:53 ` [PATCH v26 08/10] fs/ntfs3: Add Kconfig, Makefile and doc Konstantin Komarov
2021-04-02 15:53 ` [PATCH v26 09/10] fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile Konstantin Komarov
2021-04-02 15:53 ` [PATCH v26 10/10] fs/ntfs3: Add MAINTAINERS Konstantin Komarov
2021-05-19 3:47 ` [PATCH v26 00/10] NTFS read-write driver GPL implementation by Paragon Software Neal Gompa
2021-05-19 3:51 ` Neal Gompa
2021-05-20 16:13 ` Darrick J. Wong
2021-07-17 16:36 ` Pali Rohár [this message]
2021-07-25 17:02 ` Yan Pas
2021-06-07 9:55 Marius Cirsta
2021-07-28 16:23 Mohammad Rasim
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=20210717163618.vt6zjnhaiey6l64m@pali \
--to=pali@kernel.org \
--cc=aaptel@suse.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=andy.lavr@gmail.com \
--cc=anton@tuxera.com \
--cc=dan.carpenter@oracle.com \
--cc=dsterba@suse.cz \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=joe@perches.com \
--cc=kari.argillander@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=mark@harmstone.com \
--cc=nborisov@suse.com \
--cc=oleksandr@natalenko.name \
--cc=rdunlap@infradead.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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).