From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:52208 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751004AbdJLNpb (ORCPT ); Thu, 12 Oct 2017 09:45:31 -0400 Date: Thu, 12 Oct 2017 15:45:39 +0200 From: Greg KH To: Anton Altaparmakov Cc: "stable@vger.kernel.org" Subject: Re: Merging backported fscrypt to 4.4? Message-ID: <20171012134539.GA29921@kroah.com> References: <010EE55A-A5A5-49F9-AB56-980F3A25111D@tuxera.com> <20171012121139.GA11740@kroah.com> <20171012124933.GA16542@kroah.com> <0C60E331-6397-450B-A6E5-AC42091A1992@tuxera.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0C60E331-6397-450B-A6E5-AC42091A1992@tuxera.com> Sender: stable-owner@vger.kernel.org List-ID: On Thu, Oct 12, 2017 at 01:26:26PM +0000, Anton Altaparmakov wrote: > > Anyway, that's a side note, I don't really understand why you need/want > > fscrypt, if the only in-kernel filesystems that need it, already have > > this support? > > Ah, sorry for not explaining better - we have our own flash friendly > file system (TFFS), which is not in the tree so we have a vested > interest in fscrypto being part of the mainline kernel rather than > maintaining it separately. Ok, that makes more sense. No, sorry, I'm not going to make changes to any kernel for an out-of-tree chunk of code. We wouldn't do that in Linus's latest tree, so of course we wouldn't do it in a stable kernel tree. Get your filesystem merged and then we can talk :) thanks, greg k-h