public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: Amit Choudhary <amit2030@yahoo.com>,
	Bernd Petrovitsch <bernd@firmix.at>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [DISCUSS] Make the variable NULL after freeing it.
Date: Mon, 1 Jan 2007 19:36:41 +0100	[thread overview]
Message-ID: <20070101183641.GA4593@elf.ucw.cz> (raw)
In-Reply-To: <200701011709.48349.ioe-lkml@rameria.de>

Hi!

> > I decided to keep it simple. If someone is calling kfree_nullify() with anything other than a
> > simple variable, then they should call kfree().
> 
> kfree_nullify() has to replace kfree() to be of any use one day. So this is not an option.
> 

Doing kfree() that writes to its argument is not an option. kfree()
looks like a function, so it should behave as one. KFREE() might be
okay.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      parent reply	other threads:[~2007-01-01 18:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21 23:41 [PATCH] [DISCUSS] Make the variable NULL after freeing it Amit Choudhary
2006-12-27 17:10 ` Pavel Machek
2006-12-28  8:54   ` Jan Engelhardt
2006-12-31 13:38     ` Bernd Petrovitsch
2007-01-01  0:43       ` Ingo Oeser
2007-01-01  1:05         ` YOSHIFUJI Hideaki / 吉藤英明
2007-01-01  6:37         ` Amit Choudhary
2007-01-01 16:09           ` Ingo Oeser
2007-01-01 16:25             ` Andreas Schwab
2007-01-01 21:40               ` Ingo Oeser
2007-01-01 21:42                 ` Jan Engelhardt
2007-01-01 18:36             ` Pavel Machek [this message]

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=20070101183641.GA4593@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=amit2030@yahoo.com \
    --cc=bernd@firmix.at \
    --cc=ioe-lkml@rameria.de \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.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