On 6/4/07, Roland Dreier <[email protected]> wrote:
No, because as was mentioned earlier in the thread, we want code to be
able to handle 0-sized allocations without special cases. The goal is
that code like
buf = kmalloc(nobj * obj_size);
if (buf == NULL)
return -ENOMEM;
should work fine if nobj happens to be 0. But we do want to get an
oops if the code actually tries to read or write *buf.
Aah, missed that part of the discussion. Sorry for the noise ;-) - 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:
- SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Christoph Lameter <[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: Andrew Morton <[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]>
- 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]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Linus Torvalds <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: "Pekka Enberg" <[email protected]>
- Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- From: Roland Dreier <[email protected]>
- SLUB: Return ZERO_SIZE_PTR for kmalloc(0)
- Prev by Date: Re: [patch 1/2] ufd v1 - unsequential O(1) fdmap core
- Next by Date: Re: Dependent CPU core speed reporting not updated withCPUFREQ_SHARED_TYPE_HW?
- 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):
 |