Re: [PATCH] [DISCUSS] Make the variable NULL after freeing it.

In article <[email protected]> (at Mon, 1 Jan 2007 01:43:00 +0100), Ingo Oeser <[email protected]> says:

> On Sunday, 31. December 2006 14:38, Bernd Petrovitsch wrote:
> > That depends on the decision/definition if (so called) "double free" is
> > an error or not (and "free(NULL)" must work in POSIX-compliant
> > environments).
> 
> A double free of non-NULL is certainly an error.
> So the idea of setting it to NULL is ok, since then you can
> kfree the variable over and over again without any harm.

I dislike (or, say, I hate) this idea; people should fix up
such broken code paths.

--yoshfuji
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: [PATCH] [DISCUSS] Make the variable NULL after freeing it.
    • From: Jan Engelhardt <[email protected]>
  • Re: [PATCH] [DISCUSS] Make the variable NULL after freeing it.
    • From: Bernd Petrovitsch <[email protected]>
  • Re: [PATCH] [DISCUSS] Make the variable NULL after freeing it.
    • From: Ingo Oeser <[email protected]>

• Prev by Date: Re: [PATCH] [DISCUSS] Make the variable NULL after freeing it.
• Next by Date: Happy New Year (and v2.6.20-rc3 released)
• Previous by thread: Re: [PATCH] [DISCUSS] Make the variable NULL after freeing it.
• Next by thread: [patch] rcu: rcutorture suspend fix
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]