From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Continuing kallsyms failures - large kernels, XIP kernels, and large XIP kernels
Date: Fri, 30 Jan 2015 15:32:54 +0000 [thread overview]
Message-ID: <20150130153254.GL26493@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150130145642.GK26493@n2100.arm.linux.org.uk>
This is the hack I'm using to avoid the veneers appearing in the kallsyms
data. This solves my randconfig failure I saw last night - but obviously
is not bullet proof as it'll find _veneer anywhere in the symbol name.
scripts/kallsyms.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/scripts/kallsyms.c b/scripts/kallsyms.c
index c6d33bd15b04..eea599c701f5 100644
--- a/scripts/kallsyms.c
+++ b/scripts/kallsyms.c
@@ -158,6 +158,8 @@ static int read_symbol(FILE *in, struct sym_entry *s)
/* exclude debugging symbols */
else if (stype == 'N')
return -1;
+ else if (strstr(sym, "_veneer"))
+ return -1;
/* include the type field in the symbol name, so that it gets
* compressed together */
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-01-30 15:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 14:56 Continuing kallsyms failures - large kernels, XIP kernels, and large XIP kernels Russell King - ARM Linux
2015-01-30 15:32 ` Russell King - ARM Linux [this message]
2015-01-30 15:34 ` Russell King - ARM Linux
2015-01-30 17:29 ` Nicolas Pitre
2015-01-31 0:22 ` Russell King - ARM Linux
2015-02-04 0:03 ` Russell King - ARM Linux
2015-02-04 1:59 ` Nicolas Pitre
2015-02-04 9:44 ` Russell King - ARM Linux
2015-02-04 13:50 ` Nicolas Pitre
2015-02-04 14:44 ` Arnd Bergmann
2015-02-05 8:43 ` Uwe Kleine-König
2015-02-06 14:20 ` Uwe Kleine-König
2015-02-06 16:14 ` Russell King - ARM Linux
2015-02-10 8:17 ` Uwe Kleine-König
2015-02-10 19:13 ` Russell King - ARM Linux
2015-02-11 20:46 ` Stephen Rothwell
2015-02-06 20:14 ` Stefan Agner
2015-02-06 14:25 ` Uwe Kleine-König
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150130153254.GL26493@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).