On 01/13/15 at 03:50pm, Ying Xue wrote: > On 01/12/2015 08:42 PM, Thomas Graf wrote: > > On 01/12/15 at 09:38am, Ying Xue wrote: > >> Hi Thomas, > >> > >> I am really unable to see where is wrong leading to below warning > >> complaints. Can you please help me check it? > > > > Not sure yet. It's not your patch that introduced the issue though. > > It merely exposed the affected code path. > > > > Just wondering, did you test with CONFIG_DEBUG_MUTEXES enabled? > > > > > > After I enable above option, I don't find similar complaints during my > testing.
I can't reproduce it in my KVM box either so far. It looks like a mutex_lock() on an uninitialized mutex or use after free but I can't find such a code path so far. -- 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/
