From: Borislav Petkov <bp@alien8.de>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: EDAC lockdep splat
Date: Wed, 10 Jul 2013 12:41:15 +0200 [thread overview]
Message-ID: <20130710104114.GF14873@pd.tnic> (raw)
In-Reply-To: <20130710103915.GE14873@pd.tnic>
Forgot to CC him.
On Wed, Jul 10, 2013 at 12:39:15PM +0200, Borislav Petkov wrote:
> On Wed, Jul 10, 2013 at 11:57:33AM +0200, Markus Trippelsdorf wrote:
> > While debugging an unrelated issue I came across the following lockdep
> > splat:
>
> …
>
> > Jul 10 11:38:00 x4 kernel: BUG: key ffff8802169693f8 not in .data!
> > Jul 10 11:38:00 x4 kernel: ------------[ cut here ]------------
> > Jul 10 11:38:00 x4 kernel: WARNING: CPU: 3 PID: 1 at kernel/lockdep.c:2987 lockdep_init_map+0x45e/0x490()
> > Jul 10 11:38:00 x4 kernel: sda: unknown partition table
> > Jul 10 11:38:00 x4 kernel: DEBUG_LOCKS_WARN_ON(1)
>
> I know: http://marc.info/?l=linux-kernel&m=136809709202740&w=2
>
> I was expecting Mauro to fix it since his patches grew this out:
>
> commit 7a623c039075e4ea21648d88133fafa6dcfd113d
> Author: Mauro Carvalho Chehab <mchehab@redhat.com>
> Date: Mon Apr 16 16:41:11 2012 -0300
>
> edac: rewrite the sysfs code to use struct device
>
> adds struct bus_type to struct mem_ctl_info which is dynamically
> allocated and that's why lockdep complains.
>
> bus_register() needs to get a statically allocated struct bus_type as
> the rest of the kernel does it.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-07-10 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 9:57 EDAC lockdep splat Markus Trippelsdorf
2013-07-10 10:39 ` Borislav Petkov
2013-07-10 10:41 ` Borislav Petkov [this message]
2013-07-10 11:06 ` Mauro Carvalho Chehab
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=20130710104114.GF14873@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mchehab@infradead.org \
/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