Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755218AbcK2C23 (ORCPT ); Mon, 28 Nov 2016 21:28:29 -0500 Received: from imap.thunk.org ([74.207.234.97]:38738 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752592AbcK2C2W (ORCPT ); Mon, 28 Nov 2016 21:28:22 -0500 Date: Mon, 28 Nov 2016 21:27:33 -0500 From: "Theodore Ts'o" To: Eric Biggers Cc: Richard Weinberger , linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, dedekind1@gmail.com, adrian.hunter@intel.com, jaegeuk@kernel.org, david@sigma-star.at, wd@denx.de, sbabic@denx.de, dengler@linutronix.de, mhalcrow@google.com, hch@infradead.org Subject: Re: [PATCH 00/29] UBIFS File Encryption v1 Message-ID: <20161129022733.pfougb5hyw6wzdwo@thunk.org> Mail-Followup-To: Theodore Ts'o , Eric Biggers , Richard Weinberger , linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, dedekind1@gmail.com, adrian.hunter@intel.com, jaegeuk@kernel.org, david@sigma-star.at, wd@denx.de, sbabic@denx.de, dengler@linutronix.de, mhalcrow@google.com, hch@infradead.org References: <1479072072-6844-1-git-send-email-richard@nod.at> <20161114030548.eils5al7ugfhlqwg@thunk.org> <34885683-a40f-eaff-b99d-b11fc68803f7@nod.at> <20161127175241.ojvqnla4zn5mkg63@thunk.org> <698c121c-5d44-1d6f-cab8-0cbaa61e5109@nod.at> <20161128012758.GA6813@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161128012758.GA6813@google.com> User-Agent: NeoMutt/20161104 (1.7.1) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 856 Lines: 21 On Sun, Nov 27, 2016 at 05:27:58PM -0800, Eric Biggers wrote: > > Shouldn't the branch be rebased to remove the CONFIG_VMAP_STACK fixes which are > already in Linus' tree? > > fscrypto: don't use on-stack buffer for key derivation > fscrypto: don't use on-stack buffer for filename encryption > > Otherwise we'll end up with duplicate commits. Given that the ubifs folks are depending on the existing branch, having duplicate commits is considered an acceptable tradeoff to not rebasing a published commit that other trees are depending on. I tell people that the ext4.git dev branch is a rewinding branch, so people shouldn't be building other trees on top of it unless they are willing to deal with the fact that it can be rebased. However, i didn't give that warning for the fscrypt branch, so I'd much rather not rewind/rebase it. - Ted