From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Christoph Lameter" <clameter@sgi.com>,
"Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Cherwin R. Nooitmeer" <cherwin@gmail.com>,
linux-pcmcia@lists.infradead.org,
"Robert de Rooy" <robert.de.rooy@gmail.com>,
"Alan Cox" <alan@redhat.com>, "Tejun Heo" <htejun@gmail.com>,
sparclinux@vger.kernel.org, "David Miller" <davem@davemloft.net>,
"Mikael Pettersson" <mikpe@it.uu.se>,
linux1394-devel@lists.sourceforge.net,
"Stefan Richter" <stefanr@s5r6.in-berlin.de>,
"Kristian Høgsberg" <krh@bitplanet.net>,
linux-pm@lists.linux-foundation.org,
"Rafael J. Wysocki" <rjw@sisk.pl>, "Pavel Machek" <pavel@ucw.cz>,
"Marcus Better" <marcus@better.se>,
"Andrey Borzenkov" <arvidjaar@mail.ru>,
linux-usb-devel@lists.sourceforge.net,
"Greg Kroah-Hartman" <gregkh@suse.de>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: [2/3] 2.6.22-rc2: known regressions v2
Date: Thu, 24 May 2007 11:49:02 -0700 [thread overview]
Message-ID: <20070524114902.e802f327.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.0.98.0705241007290.26602@woody.linux-foundation.org>
On Thu, 24 May 2007 10:12:14 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> 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.
next prev parent reply other threads:[~2007-05-24 18:51 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46558708.2040803@googlemail.com>
2007-05-24 14:04 ` [2/3] 2.6.22-rc2: known regressions v2 Michal Piotrowski
2007-05-24 14:18 ` [linux-pm] " Alan Stern
2007-05-24 17:01 ` Christoph Lameter
2007-05-24 17:12 ` Linus Torvalds
2007-05-24 17:18 ` Christoph Lameter
2007-05-24 18:49 ` Andrew Morton [this message]
2007-05-24 19:21 ` Linus Torvalds
2007-05-24 21:02 ` Jeff Garzik
2007-05-24 19:37 ` Ingo Molnar
2007-05-24 19:50 ` Linus Torvalds
2007-05-24 20:02 ` David Woodhouse
2007-05-25 10:11 ` Ingo Molnar
2007-05-25 10:18 ` Stefan Richter
2007-05-25 16:21 ` Linus Torvalds
2007-05-25 11:53 ` Chris Newport
2007-05-25 12:34 ` Ingo Molnar
2007-05-25 16:33 ` Andrew Morton
2007-05-25 16:45 ` Christoph Lameter
2007-05-28 3:46 ` Vivek Goyal
2007-05-25 12:40 ` Stefan Richter
2007-05-25 16:45 ` Linus Torvalds
2007-05-25 17:03 ` Alan Cox
2007-05-25 17:19 ` Linus Torvalds
2007-05-25 17:37 ` Andrew Morton
2007-05-25 17:48 ` Alan Cox
2007-05-25 17:50 ` Linus Torvalds
2007-05-28 4:27 ` Vivek Goyal
2007-05-25 17:07 ` Chuck Ebbert
2007-05-25 17:21 ` Linus Torvalds
2007-05-25 18:03 ` Chris Newport
2007-05-25 20:36 ` David Miller
2007-05-26 13:16 ` [linux-pm] " Matt Sealey
2007-06-03 6:47 ` Stefan Richter
2007-05-24 14:04 ` [3/3] " Michal Piotrowski
2007-05-24 22:04 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070524114902.e802f327.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=arvidjaar@mail.ru \
--cc=cherwin@gmail.com \
--cc=clameter@sgi.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=htejun@gmail.com \
--cc=krh@bitplanet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=marcus@better.se \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mikpe@it.uu.se \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=robert.de.rooy@gmail.com \
--cc=sparclinux@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox