From: Peter Zijlstra <peterz@infradead.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: lockdep: BUG: MAX_LOCKDEP_ENTRIES too low!
Date: Thu, 19 Dec 2013 16:51:21 +0100 [thread overview]
Message-ID: <20131219155121.GL16438@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <52B3134D.2010203@oracle.com>
On Thu, Dec 19, 2013 at 10:39:57AM -0500, Sasha Levin wrote:
> That discusses lockdep classes, which is actually fine in my case. I ran out of
> MAX_LOCKDEP_ENTRIES, which isn't mentioned anywhere in Documentation/ .
Yeah, it suffers from the same problem though. Lockdep has static
resource allocation and never frees them.
The lock classes are the smallest pool and usually run out first, but
the same could happen for the entries, after all, the more classes we
have the more class connections can happen.
Anyway, barring a leak and silly class mistakes like mentioned in the
document there's nothing we can do except raise the number.
next prev parent reply other threads:[~2013-12-19 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 5:53 lockdep: BUG: MAX_LOCKDEP_ENTRIES too low! Sasha Levin
2013-12-19 10:34 ` Peter Zijlstra
2013-12-19 14:02 ` Sasha Levin
2013-12-19 15:20 ` Peter Zijlstra
2013-12-19 15:39 ` Sasha Levin
2013-12-19 15:51 ` Peter Zijlstra [this message]
2013-12-19 15:59 ` Dave Jones
2013-12-19 16:01 ` Peter Zijlstra
2013-12-19 16:10 ` Dave Jones
2013-12-19 16:51 ` Sasha Levin
2013-12-20 4:05 ` Mike Galbraith
2013-12-19 15:49 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131219155121.GL16438@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sasha.levin@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.