public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Christoph Lameter <clameter@sgi.com>,
	Satyam Sharma <satyam@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arjan van de Ven <arjan@infradead.org>,
	Tim Bird <tim.bird@am.sony.com>,
	linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: kfree(0) - ok?
Date: Sat, 18 Aug 2007 01:40:22 +0200	[thread overview]
Message-ID: <1187394022.7007.133.camel@chaos> (raw)
In-Reply-To: <84144f020708171442x52b18722k2971ceef96d3e72@mail.gmail.com>

On Sat, 2007-08-18 at 00:42 +0300, Pekka Enberg wrote:
> On 8/18/07, Christoph Lameter <clameter@sgi.com> wrote:
> > That was merged over my objections. IMHO ksize(NULL) should fail since we
> > are determining the size of an unallocated object.
> 
> Agreed, especially as we have real zero-sized objects returned from
> kmalloc() et al now.

Do we really ? 

If yes, who invented this 1980s reminiscence, where you got valid
pointers for malloc(0) ?

This is completely stupid. You do not go into a bar and order an empty
glass, just because you might eventually become thirsty later.

	tglx



  parent reply	other threads:[~2007-08-17 23:40 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14 22:59 kfree(0) - ok? Tim Bird
2007-08-14 22:55 ` Arjan van de Ven
2007-08-14 23:21   ` Jason Uhlenkott
2007-08-15  7:28     ` Jan Engelhardt
2007-08-15  8:37       ` Rene Herman
2007-08-15  9:20         ` Jan Engelhardt
2007-08-15  9:43           ` Jason Uhlenkott
2007-08-15  9:58           ` Rene Herman
2007-08-15 10:20             ` Jan Engelhardt
2007-08-15 10:27               ` Rene Herman
2007-08-15 13:58               ` Kyle Moffett
2007-08-15 14:06                 ` Jan Engelhardt
2007-08-15 14:34                   ` Kyle Moffett
2007-08-15 16:01               ` H. Peter Anvin
2007-08-15  8:52       ` Jason Uhlenkott
2007-08-15  9:18       ` Andreas Schwab
2007-08-15  9:32       ` Giacomo A. Catenazzi
2007-08-14 23:42   ` Satyam Sharma
2007-08-15  0:19     ` Christoph Lameter
2007-08-17 18:22     ` Andrew Morton
2007-08-17 18:31       ` Arjan van de Ven
2007-08-17 18:50         ` Satyam Sharma
2007-08-17 18:37       ` Jan Engelhardt
2007-08-17 20:43       ` Christoph Lameter
2007-08-17 21:17         ` Satyam Sharma
2007-08-17 21:32           ` Satyam Sharma
2007-08-17 21:13       ` Satyam Sharma
2007-08-17 21:14         ` Christoph Lameter
2007-08-17 21:42           ` Pekka Enberg
2007-08-17 23:22             ` Christoph Lameter
2007-08-17 23:40             ` Thomas Gleixner [this message]
2007-08-18  0:02               ` Satyam Sharma
2007-08-18  1:03               ` Christoph Lameter
2007-08-18  8:10               ` Pekka Enberg
2007-08-18  8:21               ` Jan Engelhardt
2007-08-17 21:46           ` Satyam Sharma
2007-08-14 23:13 ` Satyam Sharma
     [not found] <fa.oMJ6o9vN0dnAoFR83/o4hg1EptE@ifi.uio.no>
2007-08-14 23:05 ` Robert Hancock

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=1187394022.7007.133.camel@chaos \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=satyam@infradead.org \
    --cc=tim.bird@am.sony.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox