On Tue, Mar 12, 2013 at 01:18:01PM +0800, Lei Wen wrote: > > You're initializing random piece of memory which may contain any > > garbage and triggering BUG if some bit is set on it. No, you can't do > > that. debugobj is the right tool for debugging object lifetime issues > > and is already supported. > > The debugobj is not helping on this issue, I have enabled both > CONFIG_DEBUG_OBJECTS_WORK and CONFIG_DEBUG_OBJECTS. > But find they didn't report any issue at all.
It should. No idea why it didn't. Would be interesting to find out why. > And I am not init random memory, original issue is call init multi-times > for one structure and that piece of memory already been allocated. > And __INIT_WORK shouldn't call over random memory, right? Memory areas aren't always zero on allocation. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
