From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [2/3] 2.6.22-rc2: known regressions v2 Date: Thu, 24 May 2007 11:49:02 -0700 Message-ID: <20070524114902.e802f327.akpm@linux-foundation.org> References: <46558708.2040803@googlemail.com> <46559B54.80106@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Linus Torvalds Cc: "Cherwin R. Nooitmeer" , Kristian =?ISO-8859-1?Q?H=F8gsberg?= , Mikael Pettersson , Pavel Machek , sparclinux@vger.kernel.org, linux1394-devel@lists.sourceforge.net, linux-usb-devel@lists.sourceforge.net, Alan Cox , Ingo Molnar , Christoph Lameter , Robert de Rooy , Tejun Heo , Michal Piotrowski , linux-pcmcia@lists.infradead.org, Marcus Better , linux-pm@lists.linux-foundation.org, Greg Kroah-Hartman , LKML , Stefan Richter , Andrey Borzenkov , David Miller List-Id: linux-pm@vger.kernel.org On Thu, 24 May 2007 10:12:14 -0700 (PDT) Linus Torvalds wrote: > > BUG: at include/linux/slub_def.h:88 kmalloc_index() > > I'm going to change that "BUG:" to "WARNING:". I think we should remove these kmalloc(0, ...) warnings prior to the 2.6.22 release, put them back afterwards. Actually it would be useful to have some config variable which is "false" for production kernels (2.6.x, 2.6.x.y) and "true" for development kernels (2.6.x-rcN). I suspect we'd end up using this in quite a lot of places for general developer-nags which shouldn't be exposed to users of production kernels. The problem with this is that on the day Linus goes from 2.6.x-rc7 to 2.6.x we suddenly get a compile-time kernel which nobody has tested, so we'd need to set CONFIG_DEVELOPMENT_KERNEL to false around the -rc4/5 timeframe. I'm not sure how we could do this, apart from patching and unpatching a config file each time. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Date: Thu, 24 May 2007 18:49:02 +0000 Subject: Re: [2/3] 2.6.22-rc2: known regressions v2 Message-Id: <20070524114902.e802f327.akpm@linux-foundation.org> List-Id: References: <46558708.2040803@googlemail.com> <46559B54.80106@googlemail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Linus Torvalds Cc: "Cherwin R. Nooitmeer" , Kristian =?ISO-8859-1?Q?H=F8gsberg?= , Mikael Pettersson , Pavel Machek , sparclinux@vger.kernel.org, linux1394-devel@lists.sourceforge.net, linux-usb-devel@lists.sourceforge.net, Alan Cox , Ingo Molnar , Christoph Lameter , Robert de Rooy , Tejun Heo , Michal Piotrowski , linux-pcmcia@lists.infradead.org, Marcus Better , linux-pm@lists.linux-foundation.org, Greg Kroah-Hartman , LKML , Stefan Richter , Andrey Borzenkov , David Miller On Thu, 24 May 2007 10:12:14 -0700 (PDT) Linus Torvalds wrote: > > BUG: at include/linux/slub_def.h:88 kmalloc_index() > > I'm going to change that "BUG:" to "WARNING:". I think we should remove these kmalloc(0, ...) warnings prior to the 2.6.22 release, put them back afterwards. Actually it would be useful to have some config variable which is "false" for production kernels (2.6.x, 2.6.x.y) and "true" for development kernels (2.6.x-rcN). I suspect we'd end up using this in quite a lot of places for general developer-nags which shouldn't be exposed to users of production kernels. The problem with this is that on the day Linus goes from 2.6.x-rc7 to 2.6.x we suddenly get a compile-time kernel which nobody has tested, so we'd need to set CONFIG_DEVELOPMENT_KERNEL to false around the -rc4/5 timeframe. I'm not sure how we could do this, apart from patching and unpatching a config file each time. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751862AbXEXSvF (ORCPT ); Thu, 24 May 2007 14:51:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750793AbXEXSuy (ORCPT ); Thu, 24 May 2007 14:50:54 -0400 Received: from smtp1.linux-foundation.org ([207.189.120.13]:34799 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750789AbXEXSux (ORCPT ); Thu, 24 May 2007 14:50:53 -0400 Date: Thu, 24 May 2007 11:49:02 -0700 From: Andrew Morton To: Linus Torvalds Cc: Christoph Lameter , Michal Piotrowski , LKML , "Cherwin R. Nooitmeer" , linux-pcmcia@lists.infradead.org, Robert de Rooy , Alan Cox , Tejun Heo , sparclinux@vger.kernel.org, David Miller , Mikael Pettersson , linux1394-devel@lists.sourceforge.net, Stefan Richter , Kristian =?ISO-8859-1?Q?H=F8gsberg?= , linux-pm@lists.linux-foundation.org, "Rafael J. Wysocki" , Pavel Machek , Marcus Better , Andrey Borzenkov , linux-usb-devel@lists.sourceforge.net, Greg Kroah-Hartman , Ingo Molnar Subject: Re: [2/3] 2.6.22-rc2: known regressions v2 Message-Id: <20070524114902.e802f327.akpm@linux-foundation.org> In-Reply-To: References: <46558708.2040803@googlemail.com> <46559B54.80106@googlemail.com> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.6; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 24 May 2007 10:12:14 -0700 (PDT) Linus Torvalds wrote: > > BUG: at include/linux/slub_def.h:88 kmalloc_index() > > I'm going to change that "BUG:" to "WARNING:". I think we should remove these kmalloc(0, ...) warnings prior to the 2.6.22 release, put them back afterwards. Actually it would be useful to have some config variable which is "false" for production kernels (2.6.x, 2.6.x.y) and "true" for development kernels (2.6.x-rcN). I suspect we'd end up using this in quite a lot of places for general developer-nags which shouldn't be exposed to users of production kernels. The problem with this is that on the day Linus goes from 2.6.x-rc7 to 2.6.x we suddenly get a compile-time kernel which nobody has tested, so we'd need to set CONFIG_DEVELOPMENT_KERNEL to false around the -rc4/5 timeframe. I'm not sure how we could do this, apart from patching and unpatching a config file each time.