On Sat, 7 Jul 2007, Michal Piotrowski wrote:

quoted text
> > If you're looking for someone to blame, consider the fact that this has
> > gone away now I've switched back to slab. :)
> Yup, I forgot to add Christoph to CC  :)

Hmmmm.. Cannot see the corruption in the dump since it only includes 128 
bytes and it seems to have occurred way into the object. If you want to 
dump 32k to your syslog to see the corruption then look at the 
print_trailer() function and change the parameter of the call to 
print_section

	print_section("Object", p, min(s->objsize, 128));


This is a 32k sized slab and SLAB does not allow debugging on power of two 
slabs > pagesize.... No surprise that SLAB does not complain.

What are these functions "malloc" and "free"? Would be good if those 
would be using kmalloc_track_caller() so that we can figure out who called 
them.


-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/