linux-kernel - Re: Question about "Inconsistent kallsyms data"

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]

Date:	Fri, 29 Jul 2011 12:58:32 +0200
From:	Tomasz Figa <tomasz.figa@...il.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	linux-arm-kernel@...ts.infradead.org,
	Kukjin Kim <kgene.kim@...sung.com>,
	linux-kernel@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
	'Ben Dooks' <ben-linux@...ff.org>
Subject: Re: Question about "Inconsistent kallsyms data"

On Friday 29 of July 2011 at 11:02:41, Russell King - ARM Linux wrote:
> On Fri, Jul 29, 2011 at 12:00:07PM +0200, Tomasz Figa wrote:
> > Hi,
> > 
> > On Friday 29 of July 2011 at 10:48:46, Kukjin Kim wrote:
> > > Hi all,
> > > 
> > > When build with s5pc100_defconfig, happens following.
> > > 
> > > ...
> > > KSYM    .tmp_kallsyms2.S
> > > AS      .tmp_kallsyms2.o
> > > LD      vmlinux
> > > SYSMAP  System.map
> > > SYSMAP  .tmp_System.map
> > > Inconsistent kallsyms data
> > > This is a bug - please report about it
> > > Try make KALLSYMS_EXTRA_PASS=1 as a workaround
> > > make[1]: *** [vmlinux] Error 1
> > > make: *** [sub-make] Error 2
> > > 
> > > Its HEAD is following (current latest mainline)
> > > (commit 55f9c40ff632d03c527d6a6ceddcda0a224587a6)
> > > Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc
> > 
> > I can confirm that it also happens when building with s3c6400_defconfig
> > and HEAD at commit 5fd00b031530cc476240f654c078c930f1dcd6ea (Merge
> > branch 'for- linus' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/shaggy/jfs-2.6).
> > 
> > The suggested workaround (make KALLSYMS_EXTRA_PASS=1) helps, but it is
> > only a workaround and not a solution.
> > 
> > Any suggestions?
> 
> Someone want to try bisecting to find the commit?

I will try to bisect the case with s3c6400 defconfig.

--
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/