Re: kfree(NULL)

Andrew Morton writes:
> > Yes, kfree(NULL) is supposed to be uncommon.  If someone's doing it a lot
> > then we should fix up the callers.

On 4/22/06, Paul Mackerras <[email protected]> wrote:
> Well, we'd have to start by fixing up the janitors that run around
> taking out the if statements in the callers.  :)

No, it's not the janitors fault that we have paths doing lots of
kfree(NULL) calls. NULL check removal didn't create the problem, but
it makes it more visible definitely.

                                                Pekka
-
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/

---

• Follow-Ups:
  • Re: kfree(NULL)
    • From: Paul Mackerras <[email protected]>

• References:
  • kfree(NULL)
    • From: Daniel Walker <[email protected]>
  • Re: kfree(NULL)
    • From: James Morris <[email protected]>
  • Re: kfree(NULL)
    • From: Andrew Morton <[email protected]>
  • Re: kfree(NULL)
    • From: Paul Mackerras <[email protected]>

• Prev by Date: Re: [Lse-tech] [Patch 8/8] /proc export of aggregated block I/O delays
• Next by Date: Re: strncpy (maybe others) broken on Alpha
• Previous by thread: Re: kfree(NULL)
• Next by thread: Re: kfree(NULL)
• 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]