Return-Path: Received: from bombadil.infradead.org ([198.137.202.133]:58178 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725845AbeLUPx6 (ORCPT ); Fri, 21 Dec 2018 10:53:58 -0500 Date: Fri, 21 Dec 2018 07:53:54 -0800 From: Matthew Wilcox To: "Theodore Y. Ts'o" , Christoph Hellwig , Dave Chinner , "Darrick J. Wong" , Eric Biggers , linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org, Jaegeuk Kim , Victor Hsieh , Chandan Rajendra , Linus Torvalds Subject: Re: [PATCH v2 01/12] fs-verity: add a documentation file Message-ID: <20181221155354.GC10600@bombadil.infradead.org> References: <20181219071420.GC2628@infradead.org> <20181219021953.GD31274@dastard> <20181219193005.GB6889@mit.edu> <20181219213552.GO6311@dastard> <20181220220158.GC2360@mit.edu> <20181221070447.GA21687@infradead.org> <20181221154714.GA26547@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181221154714.GA26547@mit.edu> Sender: linux-ext4-owner@vger.kernel.org List-ID: On Fri, Dec 21, 2018 at 10:47:14AM -0500, Theodore Y. Ts'o wrote: > Linus --- we're going round and round, and I don't think this is > really a technical dispute at this point, but rather an aesthetics > one. Will you be willing to accept my pull request for a feature > which is being shippped on millions of Android phones, has been out > for review for months, and for which, if we *really* need to add > uselessly complicated interface later, we can do that? It's always > been the case for internal Kernel interfaces not to add code "just in > case" it's useful, but rather when a user turns up. I argue we should > be doing the same thing for user-space visible interfaces. To look at it another way, this is an aesthetic dispute in which all those who have offered opinions from outside Google -- myself, Dave Chinner & Christoph all really dislike this interface. I'd be happy to discuss alternative interfaces, particularly ones which allow for the current internal implementation, but I think this interface is really bad. In contrast to "we'll just fix it up later" (which usually applies to in-kernel interfaces), we have a policy of not breaking userspace, so accepting this interface means setting it in stone. We should get it right.