Re: [PATCH] degrade severity of lockdep printk

[Kyle McMartin]

On Mon, Mar 23, 2009 at 09:32:35PM +0100, Peter Zijlstra wrote:
> > Although I don't really see how this can be particularly fixed, since
> > any workload that allocates a struct with a lock, initializes, and then
> > eventually frees it a whole bunch of times will run out of lock_lists
> > won't it?
> 
> Not if the lock init site doesn't change. Modules are the big exception,
> cycling modules will run you out of lockdep space..
> 

Somewhat confused by this... possibly I'm just being thick and missing
some subtlety though, but surely the context is equally important?
I mean, the locks held on entry to, say, a fs_operations struct member
function could be different on every different possible callpath...

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