From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760473AbYHIDn3 (ORCPT ); Fri, 8 Aug 2008 23:43:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753766AbYHIDnV (ORCPT ); Fri, 8 Aug 2008 23:43:21 -0400 Received: from terminus.zytor.com ([198.137.202.10]:60508 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753108AbYHIDnU (ORCPT ); Fri, 8 Aug 2008 23:43:20 -0400 Message-ID: <489D1257.1040204@zytor.com> Date: Fri, 08 Aug 2008 20:43:19 -0700 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Christian Franke CC: linux-kernel@vger.kernel.org Subject: Re: [PATCH 2.6.27-rc2] block: loop device partition support References: <489CEADE.4030905@yahoo.de> In-Reply-To: <489CEADE.4030905@yahoo.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Christian Franke wrote: > From: Christian Franke > > By default, partition support of loop devices is disabled and there > seems to be no way to turn it on without changing code, if loop is not > compiled as module. > This patch introduces CONFIG_BLK_DEV_LOOP_MAXPART to make partition > support configurable via Kconfig. It keeps that feature disabled by > default for not breaking backward compatibility. The right thing would be to have a backwards compatiblity major and a new major; similar to how the md device handles it. -hpa