All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Lameter <clameter@sgi.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Srinivasa Ds <srinivasa@in.ibm.com>,
	linux-kernel@vger.kernel.org,
	Srivatsa Vaddagiri <vatsa@in.ibm.com>,
	Dinakar Guniguntala <dino@in.ibm.com>,
	pj@sgi.com, simon.derr@bull.net, clameter@cthulhu.engr.sgi.com,
	rientjes@google.com
Subject: Re: [RFC] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning
Date: Fri, 01 Jun 2007 17:46:31 -0700	[thread overview]
Message-ID: <4660BDE7.1070904@goop.org> (raw)
In-Reply-To: <alpine.LFD.0.98.0706011554300.3957@woody.linux-foundation.org>

Linus Torvalds wrote:
> So for *both* of the above reasons, it's actually stupid to return NULL 
> for a zero-sized allocation. It would be much better to return another 
> pointer that will trap on access. A good candidate might be to return
>
> 	#define BADPTR ((void *)16)
>   

I think this is a good idea in principle, but I wonder if there's any
code which assumes that kmalloc(x) != kmalloc(x) for all non-NULL
returns from kmalloc.

J

  parent reply	other threads:[~2007-06-02  0:46 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01  7:27 [RFC] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning Srinivasa Ds
2007-06-01 10:50 ` Srinivasa Ds
2007-06-01 18:13   ` Christoph Lameter
2007-06-01 19:11     ` Paul Jackson
2007-06-01 19:18       ` Christoph Lameter
2007-06-01 19:47         ` Paul Jackson
2007-06-01 19:51           ` Christoph Lameter
2007-06-01 20:02             ` Paul Jackson
2007-06-01 20:06               ` Christoph Lameter
2007-06-01 20:19                 ` Paul Jackson
2007-06-01 20:43                   ` Christoph Lameter
2007-06-01 20:54                     ` Paul Jackson
2007-06-01 20:30   ` Jeremy Fitzhardinge
2007-06-01 20:44     ` Paul Jackson
2007-06-01 20:47     ` Christoph Lameter
2007-06-01 20:56       ` Jeremy Fitzhardinge
2007-06-01 20:59       ` Andrew Morton
2007-06-01 21:45         ` Christoph Lameter
2007-06-01 22:16           ` Andrew Morton
2007-06-01 22:20             ` Christoph Lameter
2007-06-01 22:33               ` Andrew Morton
2007-06-01 22:41                 ` Christoph Lameter
2007-06-01 23:00                   ` Linus Torvalds
2007-06-01 23:29                     ` Christoph Lameter
2007-06-01 23:41                       ` Linus Torvalds
2007-06-01 23:46                         ` Christoph Lameter
2007-06-01 23:57                           ` Linus Torvalds
2007-06-02  0:12                             ` Christoph Lameter
2007-06-02  0:16                             ` Andrew Morton
2007-06-02  0:26                               ` Christoph Lameter
2007-06-02  1:04                                 ` Linus Torvalds
2007-06-02  0:46                     ` Jeremy Fitzhardinge [this message]
2007-06-02  1:05                     ` Valdis.Kletnieks
2007-06-02  1:24                       ` Christoph Lameter
2007-06-01 23:02                   ` Andrew Morton
2007-06-01 23:16                     ` Christoph Lameter
2007-06-01 23:21                       ` Christoph Lameter
2007-06-01 23:36                       ` Linus Torvalds
2007-06-01 23:42                         ` Christoph Lameter
2007-06-01 23:25                     ` Linus Torvalds
2007-06-02  0:41                   ` Jeremy Fitzhardinge
2007-06-02  0:43             ` Jeremy Fitzhardinge
2007-06-02  0:51               ` Andrew Morton
2007-06-02  0:59                 ` Jeremy Fitzhardinge

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=4660BDE7.1070904@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@cthulhu.engr.sgi.com \
    --cc=clameter@sgi.com \
    --cc=dino@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    --cc=rientjes@google.com \
    --cc=simon.derr@bull.net \
    --cc=srinivasa@in.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vatsa@in.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.