linux-kernel - Re: EDAC lockdep splat

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]

Message-ID: <20130710103915.GE14873@pd.tnic>
Date:	Wed, 10 Jul 2013 12:39:15 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Markus Trippelsdorf <markus@...ppelsdorf.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: EDAC lockdep splat

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@...hat.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.
--
--
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/