Re: [PATCH] include/linux/slab.h: new KFREE() macro.

On 1/8/07, Amit Choudhary <[email protected]> wrote:

It is a programming error because the underlying code cannot handle it.

Yes. Do you also grasp the fact that there is no way for the allocator
to handle it either? So, double-free, from allocator standpoint can
_never_ be no-op.

What you're proposing is _not_ making double-free no-op, but instead,
making sure we never have a reference to p after kfree(p). However,
(1) that bloats the kernel text and (2) doesn't actually guarantee
that there are _no_ references to p (you can have an alias q for it,
but there's no way for us to know that).
-
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] include/linux/slab.h: new KFREE() macro.
    • From: "Pekka Enberg" <[email protected]>
  • Re: [PATCH] include/linux/slab.h: new KFREE() macro.
    • From: Amit Choudhary <[email protected]>

• Prev by Date: Re: [announce] [patch] KVM paravirtualization for Linux
• Next by Date: Re: [announce] [patch] KVM paravirtualization for Linux
• Previous by thread: Re: [PATCH] include/linux/slab.h: new KFREE() macro.
• Next by thread: Re: [PATCH] include/linux/slab.h: new KFREE() macro.
• 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]