Re: MAX_LOCKDEP_ENTRIES too low (called from ioc_release_fn)

2012-10-19 Thread Dave Jones
On Fri, Oct 19, 2012 at 02:49:32PM +0200, Peter Zijlstra wrote: > Of course, if you do run out of lock classes, the next thing to do is > to find the offending lock classes. First, the following command gives > you the number of lock classes currently in use along with the maximum: > >

Re: MAX_LOCKDEP_ENTRIES too low (called from ioc_release_fn)

2012-10-19 Thread Peter Zijlstra
On Fri, 2012-10-19 at 01:21 -0400, Dave Jones wrote: > > Not sure why you are CC'ing a call site, rather than the maintainers of > > the code. Just looks like lockdep is using too small a static value. > > Though it is pretty darn large... > > You're right, it's a huge chunk of memory. > It

Re: MAX_LOCKDEP_ENTRIES too low (called from ioc_release_fn)

2012-10-19 Thread Peter Zijlstra
On Fri, 2012-10-19 at 01:21 -0400, Dave Jones wrote: Not sure why you are CC'ing a call site, rather than the maintainers of the code. Just looks like lockdep is using too small a static value. Though it is pretty darn large... You're right, it's a huge chunk of memory. It looks like

Re: MAX_LOCKDEP_ENTRIES too low (called from ioc_release_fn)

2012-10-19 Thread Dave Jones
On Fri, Oct 19, 2012 at 02:49:32PM +0200, Peter Zijlstra wrote: Of course, if you do run out of lock classes, the next thing to do is to find the offending lock classes. First, the following command gives you the number of lock classes currently in use along with the maximum:

Re: MAX_LOCKDEP_ENTRIES too low (called from ioc_release_fn)

2012-10-18 Thread Dave Jones
On Thu, Oct 18, 2012 at 07:53:08AM +0200, Jens Axboe wrote: > On 2012-10-18 03:53, Dave Jones wrote: > > Triggered while fuzz testing.. > > > > > > BUG: MAX_LOCKDEP_ENTRIES too low! > > turning off the locking correctness validator. > > Pid: 22788, comm: kworker/2:1 Not tainted 3.7.0-rc1+

Re: MAX_LOCKDEP_ENTRIES too low (called from ioc_release_fn)

2012-10-18 Thread Dave Jones
On Thu, Oct 18, 2012 at 07:53:08AM +0200, Jens Axboe wrote: On 2012-10-18 03:53, Dave Jones wrote: Triggered while fuzz testing.. BUG: MAX_LOCKDEP_ENTRIES too low! turning off the locking correctness validator. Pid: 22788, comm: kworker/2:1 Not tainted 3.7.0-rc1+ #34 Call

Re: MAX_LOCKDEP_ENTRIES too low (called from ioc_release_fn)

2012-10-17 Thread Jens Axboe
On 2012-10-18 03:53, Dave Jones wrote: > Triggered while fuzz testing.. > > > BUG: MAX_LOCKDEP_ENTRIES too low! > turning off the locking correctness validator. > Pid: 22788, comm: kworker/2:1 Not tainted 3.7.0-rc1+ #34 > Call Trace: > [] add_lock_to_list.isra.29.constprop.45+0xdd/0xf0 > []

MAX_LOCKDEP_ENTRIES too low (called from ioc_release_fn)

2012-10-17 Thread Dave Jones
Triggered while fuzz testing.. BUG: MAX_LOCKDEP_ENTRIES too low! turning off the locking correctness validator. Pid: 22788, comm: kworker/2:1 Not tainted 3.7.0-rc1+ #34 Call Trace: [] add_lock_to_list.isra.29.constprop.45+0xdd/0xf0 [] __lock_acquire+0x1121/0x1ba0 [] lock_acquire+0xa2/0x220

MAX_LOCKDEP_ENTRIES too low (called from ioc_release_fn)

2012-10-17 Thread Dave Jones
Triggered while fuzz testing.. BUG: MAX_LOCKDEP_ENTRIES too low! turning off the locking correctness validator. Pid: 22788, comm: kworker/2:1 Not tainted 3.7.0-rc1+ #34 Call Trace: [810decdd] add_lock_to_list.isra.29.constprop.45+0xdd/0xf0 [810e2871]

Re: MAX_LOCKDEP_ENTRIES too low (called from ioc_release_fn)

2012-10-17 Thread Jens Axboe
On 2012-10-18 03:53, Dave Jones wrote: Triggered while fuzz testing.. BUG: MAX_LOCKDEP_ENTRIES too low! turning off the locking correctness validator. Pid: 22788, comm: kworker/2:1 Not tainted 3.7.0-rc1+ #34 Call Trace: [810decdd] add_lock_to_list.isra.29.constprop.45+0xdd/0xf0