Re: lockdep: strange %s#5 lock name

On Thu, Feb 13, 2014 at 04:26:45PM -0500, Tejun Heo wrote:
> > It seems to me that when the second time alloc_workqueue() is called
> > from the same code path, it would have two locks with the same key, but
> > not the same &wq->name, which doesn't meet lockdep's assumption.
> 
> Dang...  I reverted the previous patch for now.  Peter, does this
> approach sound good to you?

Whatever works I suppose; like Li said; a little ugly but not sure we
can do better.