linux-kernel - Re: pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002 lockdep_init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 7 May 2015 19:06:26 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Tvrtko Ursulin <tvrtko.ursulin@...ux.intel.com>
Cc:	Tejun Heo <tj@...nel.org>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...hat.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	NeilBrown <neilb@...e.de>
Subject: Re: pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002
 lockdep_init_map

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/