Re: [RFC 1/3] SLUB: slab_ops instead of constructors / destructors

[email protected] wrote:
> +	if (ctor || dtor) {
> +		so = kzalloc(sizeof(struct slab_ops), GFP_KERNEL);
> +		so->ctor = ctor;
> +		so->dtor = dtor;
> +	}
> +	return  __kmem_cache_create(s, size, align, flags, so);
Is this a memory leak?

Regards
Bert Wesarg
-
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: [RFC 1/3] SLUB: slab_ops instead of constructors / destructors
    • From: "Satyam Sharma" <[email protected]>

• References:
  • [RFC 0/3] Slab Defrag / Slab Targeted Reclaim and general Slab API changes
    • From: [email protected]
  • [RFC 1/3] SLUB: slab_ops instead of constructors / destructors
    • From: [email protected]

• Prev by Date: [PATCH] trivial: update broken URLs in Documentation/filesystems
• Next by Date: Re: Correct location for ADC/DAC drivers
• Previous by thread: Re: [RFC 1/3] SLUB: slab_ops instead of constructors / destructors
• Next by thread: Re: [RFC 1/3] SLUB: slab_ops instead of constructors / destructors
• 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]