RE: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1)

RE: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1)

[Konstantin Komarov]

> From: Linus Torvalds <torvalds@linux-foundation.org>
> Sent: Friday, July 30, 2021 8:24 PM
> To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>; Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Leonidas P. Papadakos <papadakospan@gmail.com>; zajec5@gmail.com; Darrick J. Wong <djwong@kernel.org>; Greg Kroah-
> Hartman <gregkh@linuxfoundation.org>; Hans de Goede <hdegoede@redhat.com>; linux-fsdevel <linux-fsdevel@vger.kernel.org>;
> Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Al Viro <viro@zeniv.linux.org.uk>; Matthew Wilcox <willy@infradead.org>
> Subject: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1)
> 
> On Fri, Jul 30, 2021 at 8:55 AM Konstantin Komarov
> <almaz.alexandrovich@paragon-software.com> wrote:
> >
> > We've just sent the 27th patch series which fixes to the buildability against
> > current linux-next. And we'll need several days to prepare a proper pull request
> > before sending it to you.
> 
> Well, I won't pull until the next merge window opens anyway (about a
> month away). But it would be good to have your tree in linux-next for
> at least a couple of weeks before that happens.
> 
> Added Stephen to the participants list as a heads-up for him - letting
> him know where to fetch the git tree from will allow that to happen if
> you haven't done so already.
> 

Thanks for this clarification, Linus!
Stephen, please find the tree here:
https://github.com/Paragon-Software-Group/linux-ntfs3.git
It is the fork from 5.14-rc5 tag with ntfs3 patches applied.
Also, the latest changes
- fix some generic/XYZ xfstests, which were discussed
with Theodore, Darrick and others
- updates the MAINTAINERS with mailing list (also added to CC here) and scm tree link.

Please let me know if additional changes requred to get fetched into linux-next.

> The one other thing I do want when there's big new pieces like this
> being added is to ask you to make sure that everything is signed-off
> properly, and that there is no internal confusion about the GPLv2
> inside Paragon, and that any legal people etc are all aware of this
> all and are on board. The last thing we want to see is some "oops, we
> didn't mean to do this" brouhaha six months later.
> 
> I doubt that's an issue, considering how public this all has been, but
> I just wanted to mention it just to be very obvious about it.
> 
>                   Linus
Indeed, there is no internal confusion about the GPLv2 and we mean to make this contribution.

Best regards,
Konstantin.

Re: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1)

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 3031 bytes --]

Hi Konstantin,

On Fri, 13 Aug 2021 16:11:10 +0000 Konstantin Komarov <almaz.alexandrovich@paragon-software.com> wrote:
>
> > From: Linus Torvalds <torvalds@linux-foundation.org>
> > Sent: Friday, July 30, 2021 8:24 PM
> > To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>; Stephen Rothwell <sfr@canb.auug.org.au>
> > Cc: Leonidas P. Papadakos <papadakospan@gmail.com>; zajec5@gmail.com; Darrick J. Wong <djwong@kernel.org>; Greg Kroah-
> > Hartman <gregkh@linuxfoundation.org>; Hans de Goede <hdegoede@redhat.com>; linux-fsdevel <linux-fsdevel@vger.kernel.org>;
> > Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Al Viro <viro@zeniv.linux.org.uk>; Matthew Wilcox <willy@infradead.org>
> > Subject: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1)
> > 
> > On Fri, Jul 30, 2021 at 8:55 AM Konstantin Komarov
> > <almaz.alexandrovich@paragon-software.com> wrote:  
> > >
> > > We've just sent the 27th patch series which fixes to the buildability against
> > > current linux-next. And we'll need several days to prepare a proper pull request
> > > before sending it to you.  
> > 
> > Well, I won't pull until the next merge window opens anyway (about a
> > month away). But it would be good to have your tree in linux-next for
> > at least a couple of weeks before that happens.
> > 
> > Added Stephen to the participants list as a heads-up for him - letting
> > him know where to fetch the git tree from will allow that to happen if
> > you haven't done so already.
> >   
> 
> Thanks for this clarification, Linus!
> Stephen, please find the tree here:
> https://github.com/Paragon-Software-Group/linux-ntfs3.git
> It is the fork from 5.14-rc5 tag with ntfs3 patches applied.
> Also, the latest changes
> - fix some generic/XYZ xfstests, which were discussed
> with Theodore, Darrick and others
> - updates the MAINTAINERS with mailing list (also added to CC here) and scm tree link.
> 
> Please let me know if additional changes requred to get fetched into linux-next.

Added from today.  It looks good, we will see how it goes when integrated/built.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1)

[Kari Argillander]

On Fri, Aug 13, 2021 at 04:11:10PM +0000, Konstantin Komarov wrote:
> > From: Linus Torvalds <torvalds@linux-foundation.org>
> > Sent: Friday, July 30, 2021 8:24 PM
> > To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>; Stephen Rothwell <sfr@canb.auug.org.au>
> > Cc: Leonidas P. Papadakos <papadakospan@gmail.com>; zajec5@gmail.com; Darrick J. Wong <djwong@kernel.org>; Greg Kroah-
> > Hartman <gregkh@linuxfoundation.org>; Hans de Goede <hdegoede@redhat.com>; linux-fsdevel <linux-fsdevel@vger.kernel.org>;
> > Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Al Viro <viro@zeniv.linux.org.uk>; Matthew Wilcox <willy@infradead.org>
> > Subject: Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1)
> > 
> > On Fri, Jul 30, 2021 at 8:55 AM Konstantin Komarov
> > <almaz.alexandrovich@paragon-software.com> wrote:
> > >
> > > We've just sent the 27th patch series which fixes to the buildability against
> > > current linux-next. And we'll need several days to prepare a proper pull request
> > > before sending it to you.
> > 
> > Well, I won't pull until the next merge window opens anyway (about a
> > month away). But it would be good to have your tree in linux-next for
> > at least a couple of weeks before that happens.
> > 
> > Added Stephen to the participants list as a heads-up for him - letting
> > him know where to fetch the git tree from will allow that to happen if
> > you haven't done so already.
> > 
> 
> Thanks for this clarification, Linus!
> Stephen, please find the tree here:
> https://github.com/Paragon-Software-Group/linux-ntfs3.git
> It is the fork from 5.14-rc5 tag with ntfs3 patches applied.
> Also, the latest changes
> - fix some generic/XYZ xfstests, which were discussed
> with Theodore, Darrick and others
> - updates the MAINTAINERS with mailing list (also added to CC here) and scm tree link.

Can you please send this also as normal patch series to mailing lists so
we can comment there.

One thing a like to ask you to do before that is add reviewed-by tag
and signed-off-by tag as stated here
https://lore.kernel.org/linux-fsdevel/20210810054637.aap4zuiiparfl2gq@kari-VirtualBox/
and
https://lore.kernel.org/linux-fsdevel/20210810074740.mkjcow2inyjaakch@kari-VirtualBox/

> Please let me know if additional changes requred to get fetched into linux-next.
> 
> > The one other thing I do want when there's big new pieces like this
> > being added is to ask you to make sure that everything is signed-off
> > properly, and that there is no internal confusion about the GPLv2
> > inside Paragon, and that any legal people etc are all aware of this
> > all and are on board. The last thing we want to see is some "oops, we
> > didn't mean to do this" brouhaha six months later.
> > 
> > I doubt that's an issue, considering how public this all has been, but
> > I just wanted to mention it just to be very obvious about it.
> > 
> >                   Linus
> Indeed, there is no internal confusion about the GPLv2 and we mean to make this contribution.
> 
> Best regards,
> Konstantin.