On Mon, 4 Jun 2007, Pekka Enberg wrote: > I thought the whole point of this patch was to get rid of the WARN_ON > as you will get a nice oops if you dereference the pointer? That is another patchset. See http://marc.info/?l=linux-kernel&w=2&r=1&s=DEVELKERNEL&q=b - 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: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Pekka Enberg <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- References:
- SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Christoph Lameter <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Linus Torvalds <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Christoph Lameter <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: "Pekka Enberg" <[email protected]>
- SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- Prev by Date: Re: [PATCH 00/10] Containers(V10): Generic Process Containers
- Next by Date: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
- Previous by thread: Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- Next by thread: Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- Index(es):
 |