On 01/31/2012 01:57 AM, Jeff Layton wrote: > WARNING: at lib/debugobjects.c:262 debug_print_object+0x8c/0xb0() > > For now, this patch is really just papering over that problem, but it > should be "mostly harmless". That said, I'm ok with dropping it if > Thomas is planning to fix this in the debugobjects code however. > I disagree it's harmless. What if kmem_cache_free/kmem_cache_alloc deploys a poisoning schema, in debug mode. Which stumps over memory. Is it initialized then? What was the last state of the timer, is it safe for resume? For us this is a new object we should initialize it. Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
