From: David Sterba <dsterba@suse.cz> To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com> Cc: "viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org> Subject: Re: [PATCH] fs: NTFS read-write driver GPL implementation by Paragon Software. Date: Fri, 14 Aug 2020 15:40:57 +0200 [thread overview] Message-ID: <20200814134056.GV2026@twin.jikos.cz> (raw) In-Reply-To: <2911ac5cd20b46e397be506268718d74@paragon-software.com> On Fri, Aug 14, 2020 at 12:29:01PM +0000, Konstantin Komarov wrote: > This patch adds NTFS Read-Write driver to fs/ntfs3. > > Having decades of expertise in commercial file systems development and huge > test coverage, we at Paragon Software GmbH want to make our contribution to > the Open Source Community by providing implementation of NTFS Read-Write > driver for the Linux Kernel. > > This is fully functional NTFS Read-Write driver. Current version works with > NTFS(including v3.1) normal/compressed/sparse files and supports journal replaying. > > We plan to support this version after the codebase once merged, and add new > features and fix bugs. For example, full journaling support over JBD will be > added in later updates. > > The patch is too big to handle it within an e-mail body, so it is available to download > on our server: https://dl.paragon-software.com/ntfs3/ntfs3.patch > > Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com> In case somebody wants to compile it, this fixup is needed to let 'make fs/ntfs3/' actually work, besides enabling it in the config. diff --git a/fs/Makefile b/fs/Makefile index 1c7b0e3f6daa..b0b4ad8affa0 100644 --- a/fs/Makefile +++ b/fs/Makefile @@ -100,6 +100,7 @@ obj-$(CONFIG_SYSV_FS) += sysv/ obj-$(CONFIG_CIFS) += cifs/ obj-$(CONFIG_HPFS_FS) += hpfs/ obj-$(CONFIG_NTFS_FS) += ntfs/ +obj-$(CONFIG_NTFS3_FS) += ntfs3/ obj-$(CONFIG_UFS_FS) += ufs/ obj-$(CONFIG_EFS_FS) += efs/ obj-$(CONFIG_JFFS2_FS) += jffs2/ diff --git a/fs/ntfs3/Makefile b/fs/ntfs3/Makefile index 4d4fe198b8b8..d99dd1af43aa 100644 --- a/fs/ntfs3/Makefile +++ b/fs/ntfs3/Makefile @@ -5,7 +5,7 @@ obj-$(CONFIG_NTFS3_FS) += ntfs3.o -ntfs3-objs := bitfunc.o bitmap.o inode.o fsntfs.o frecord.o \ +ntfs3-y := bitfunc.o bitmap.o inode.o fsntfs.o frecord.o \ index.o attrlist.o record.o attrib.o run.o xattr.o\ upcase.o super.o file.o dir.o namei.o lznt.o\ fslog.o ---
next prev parent reply other threads:[~2020-08-14 13:42 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-14 12:29 Konstantin Komarov 2020-08-14 13:17 ` Nikolay Borisov 2020-08-14 13:40 ` David Sterba [this message] 2020-08-20 9:26 ` Konstantin Komarov 2020-08-20 10:59 ` Konstantin Komarov 2020-08-14 14:08 ` Aurélien Aptel 2020-08-20 10:20 ` Konstantin Komarov 2020-08-14 15:30 ` Aurélien Aptel 2020-08-20 10:38 ` Konstantin Komarov 2020-08-15 19:06 ` David Sterba 2020-08-16 0:42 ` Matthew Wilcox 2020-08-20 10:48 ` Konstantin Komarov 2020-08-16 7:56 ` Pali Rohár
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=20200814134056.GV2026@twin.jikos.cz \ --to=dsterba@suse.cz \ --cc=almaz.alexandrovich@paragon-software.com \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=viro@zeniv.linux.org.uk \ --subject='Re: [PATCH] fs: NTFS read-write driver GPL implementation by Paragon Software.' \ /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
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).