On Fri, 1 Jun 2007, Andrew Morton wrote: > Poisoning and redzoning could have caught that. Redzoning would not have caught it. This was a kmalloc allocation and SLAB always gave them 32 bytes to play with. Only writes more than 32 bytes behind would have been caught. Poisoning is only applicable to unallocated objects and these were allocated. - 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] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning
- From: Andrew Morton <[email protected]>
- Re: [RFC] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning
- References:
- [RFC] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning
- From: Srinivasa Ds <[email protected]>
- Re: [RFC] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning
- From: Srinivasa Ds <[email protected]>
- Re: [RFC] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [RFC] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning
- From: Christoph Lameter <[email protected]>
- Re: [RFC] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning
- From: Andrew Morton <[email protected]>
- [RFC] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning
- Prev 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?
- Next by Date: Re: Extending boot protocol & bzImage for paravirt_ops
- Previous by thread: Re: [RFC] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning
- Next by thread: Re: [RFC] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning
- Index(es):
 |