Re: EDAC lockdep splat

[Mauro Carvalho Chehab]

Hi Boris/Markus,

Em Wed, 10 Jul 2013 12:41:15 +0200
Borislav Petkov <bp@xxxxxxxxx> escreveu:

> 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@xxxxxxxxxx>
> > 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.
> 

I'm currently without any systems where I could try to reproduce it, as
I moved to a new job at Samsung, and I'm still in the process of getting
access to the corporate facilities and to get the needed hardware.
The hardware I currently own doesn't support EDAC.

So, I doubt that I would be able to touch on that in the next couple
weeks or so.

If you're urging for a fix, feel free to propose a patch.
Otherwise, I'll take care of it as soon as I receive the hardware.

Regards,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/