From: Peter Zijlstra <peterz@infradead.org>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
NeilBrown <neilb@suse.de>
Subject: Re: pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002 lockdep_init_map
Date: Thu, 7 May 2015 19:06:26 +0200 [thread overview]
Message-ID: <20150507170626.GA27504@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <554B9305.301@linux.intel.com>
On Thu, May 07, 2015 at 05:29:57PM +0100, Tvrtko Ursulin wrote:
> >>> May 7 11:58:20 skl kernel: [ 6.066696] futex hash table entries: 1024 (order: 5, 131072 bytes)
> >>> May 7 11:58:20 skl kernel: [ 6.329549] HugeTLB registered 2 MB page size, pre-allocated 0 pages
> > sysfs by default uses lockdep key embedded in attrs. It looks like
> > somebody is making on-heap copies of attrs and using them as the group
> > attrs. What's the offending pmu type?
>
> I am not familiar with this area, is this the answer?
Nope, that's way before you get the fail. initcall_debug might get you
the right answer, but I suspect its the intel_uncore driver.
I see arch/x86/kernel/cpu/perf_event_intel_uncore.c:uncore_type_init()
do exactly what TJ says, its dynamically allocating struct attribute.
Now, let me try and trigger that locally, that should not be skylake
specific at all.
next prev parent reply other threads:[~2015-05-07 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 13:54 pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002 lockdep_init_map Tvrtko Ursulin
2015-05-07 14:05 ` Peter Zijlstra
2015-05-07 16:25 ` Tejun Heo
2015-05-07 16:29 ` Tvrtko Ursulin
2015-05-07 17:06 ` Peter Zijlstra [this message]
2015-05-07 17:29 ` Peter Zijlstra
2015-05-08 14:38 ` Tvrtko Ursulin
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=20150507170626.GA27504@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@suse.de \
--cc=tj@kernel.org \
--cc=tvrtko.ursulin@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).