linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	gustavold@linux.vnet.ibm.com
Subject: Re: powerpc/perf/24x7: Fix lockdep warning
Date: Wed,  8 Jul 2015 20:54:08 +1000 (AEST)	[thread overview]
Message-ID: <20150708105409.131F7140B0D@ozlabs.org> (raw)
In-Reply-To: <20150707193725.GA12395@us.ibm.com>

On Tue, 2015-07-07 at 19:37:25 UTC, Sukadev Bhattiprolu wrote:
> >From 370152d9427e57cd9632b00189f71099f8e85544 Mon Sep 17 00:00:00 2001
> From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> Date: Tue, 7 Jul 2015 12:21:10 -0400
> Subject: [PATCH 1/1] powerpc/perf/24x7: Fix lockdep warning
> 
> The sysfs attributes for the 24x7 counters are dynamically allocated.
> Initialize the attributes using sysfs_attr_init() to fix following
> warning which occurs when CONFIG_DEBUG_LOCK_VMALLOC=y.
> 
> [    0.346249] audit: initializing netlink subsys (disabled)
> [    0.346284] audit: type=2000 audit(1436295254.340:1): initialized
> [    0.346489] BUG: key c0000000efe90198 not in .data!
> [    0.346491] DEBUG_LOCKS_WARN_ON(1)
> [    0.346502] ------------[ cut here ]------------
> [    0.346504] WARNING: at ../kernel/locking/lockdep.c:3002
> [    0.346506] Modules linked in:
> 
> Reported-by: Gustavo Luiz Duarte <gustavold@linux.vnet.ibm.com>
> Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> Tested-by: Gustavo Luiz Duarte <gustavold@linux.vnet.ibm.com>

Applied to powerpc fixes, thanks.

https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=442053e57a4fc58b719b6ceab60f29ef9cf4404c

cheers

      parent reply	other threads:[~2015-07-08 10:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 19:37 [PATCH] powerpc/perf/24x7: Fix lockdep warning Sukadev Bhattiprolu
2015-07-07 20:54 ` Gustavo Luiz Duarte
2015-07-08 10:54 ` Michael Ellerman [this message]

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=20150708105409.131F7140B0D@ozlabs.org \
    --to=mpe@ellerman.id.au \
    --cc=gustavold@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sukadev@linux.vnet.ibm.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).