linux-kernel - Re: "Inconsistent kallsyms data" error

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 for Android: free password hash cracker in your pocket

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

Date:	Sun, 15 Jul 2012 23:58:53 +0200
From:	Domenico Andreoli <cavokz@...il.com>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	Paulo Marques <pmarques@...popie.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Sam Ravnborg <sam@...nborg.org>, Michal Marek <mmarek@...e.cz>,
	Arnaud Lacombe <lacombar@...il.com>,
	Nick Bowler <nbowler@...iptictech.com>,
	Jan Beulich <jbeulich@...ell.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: "Inconsistent kallsyms data" error

On Sat, Jul 07, 2012 at 12:48:23AM -0400, Paul Gortmaker wrote:
> On Fri, Jul 6, 2012 at 7:17 AM, Paulo Marques <pmarques@...popie.com> wrote:
> 
> [...]
> 
> >
> > There was a recent thread from David Brown on the arm linux mailing list
> > ("ARM: two possible fixes for the KALLSYMS build problem"). He tracked
> > down the problem to having empty per_cpu sections on a non-smp build.
> 
> Actually rmk diagnosed it as the empty per_cpu sections.  See it here:
> 
> http://marc.info/?l=linux-next&m=133267456809502&w=2

I also saw this problem in the past (a couple of months ago), mostly on a
specific machine. But I _am_ playing with the linker scripts so I expected
to be the cause in an unknown way.

Unfortunately I've never understood the cause (I also switched from reiserfs
to ext4 in the panic, moving the source tree around seemed to help). The
behaviour seemed inconsistent and could not reliably reproduce it even if
there were very few "moving targets". Very clueless.

Don't know why I'm not encountering it any more but a more useful diagnostic
would be surely useful.  The second pass thing didn't help me either. I
also tried to implement an addition pass but the thing was not making any
sense to me anyway.

So yes, in case of error please leave some trace somewhere so that to poor
user has some chance to work his/her good luck out of the troubles.

cheers,
Domenico
--
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/