From: Christoph Hellwig Subject: Re: [git pull] device mapper changes for 4.21 Date: Sun, 30 Dec 2018 01:06:46 -0800 Message-ID: <20181230090646.GB1022@infradead.org> References: <20181227160944.GA12190@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20181227160944.GA12190@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Mike Snitzer Cc: Sweet Tea , wuzhouhui , AliOS system security , Nikos Tsironis , Eric Biggers , Heinz Mauelshagen , Shenghui Wang , linux-block@vger.kernel.org, dm-devel@redhat.com, Mikulas Patocka , Jaegeuk Kim , Colin Ian King , Linus Torvalds , Milan Broz , Alasdair G Kergon List-Id: dm-devel.ids On Thu, Dec 27, 2018 at 11:09:44AM -0500, Mike Snitzer wrote: > - Fix various DM targets to check for device sector overflow if > CONFIG_LBDAF is not set. Question to Jens and Linus: is there any good reason to keep the CONFIG_LBDAF=n option around? Less than 2gig block devices seem to be an absolutele niche, and I wonder if it is still worth maintaining the special case just for that.