linux-kernel - Re: maps mismatch in /proc/kcore for sparc

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:	Wed, 18 Mar 2015 15:43:59 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	david.ahern@...cle.com
Cc:	linux-kernel@...r.kernel.org, sparclinux@...r.kernel.org
Subject: Re: maps mismatch in /proc/kcore for sparc

From: David Ahern <david.ahern@...cle.com>
Date: Wed, 18 Mar 2015 10:56:22 -0600

> I am trying to understand why the perf tool on sparc fails to convert
> kernel symbols when /proc/kcore is used. I have instrumented perf to
> the point I can see that it drops symbols from kallsyms because it
> cannot find a corresponding map when the kernel maps are created based
> on parsing /proc/kcore.

I'm looking into this, I think we need to set ARCH_PROC_KCORE_TEXT in
arch/sparc/Kconfig

I have an even worse problem on my T4 system, /proc/kcore is zero
length.  Looking into that now as well.
--
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/