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
| ||
|
Date: Thu, 31 Oct 2013 15:43:11 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Ming Lei <tom.leiming@...il.com> Cc: linux-kernel@...r.kernel.org, Rusty Russell <rusty@...tcorp.com.au>, Russell King <linux@....linux.org.uk>, linux-arm-kernel@...ts.infradead.org, Michal Marek <mmarek@...e.cz> Subject: Re: [PATCH] scripts/kallsyms: filter symbols not in kernel address space On Mon, 28 Oct 2013 23:48:59 +0800 Ming Lei <tom.leiming@...il.com> wrote: > This patch uses CONFIG_PAGE_OFFSET to filter symbols which > are not in kernel address space because these symbols are > generally for generating code purpose and can't be run at > kernel mode, so we needn't keep them in /proc/kallsyms. > > For example, on ARM there are some symbols which are > linked in relocatable code section, then perf can't parse > symbols any more from /proc/kallsyms, and this patch fixes > the problem. This is a non-back-compatible change and I'd like to see a much stronger assurance that it is safe to merge and will not break any existing application on the planet, please. For a start, please describe with great precision what these excluded symbols are (examples would help) and explain why no application will conceivably have had any use for them. -- 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/
Powered by blists - more mailing lists