From: Paulo Marques <pmarques@grupopie.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: [-mm PATCH] kallsyms should prefer non weak symbols
Date: Tue, 04 Dec 2007 20:35:32 +0000 [thread overview]
Message-ID: <4755BA14.8060706@grupopie.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
When resolving symbol names from addresses with aliased symbol names,
kallsyms_lookup always returns the first symbol, even if it is a weak
symbol.
This patch changes this by sorting the symbols with the weak symbols
last before feeding them to the kernel. This way the kernel runtime
isn't changed at all, only the kallsyms build system is changed.
Another side effect is that the symbols get sorted by address, too. So,
even if future binutils version have some bug in "nm" that makes it fail
to correctly sort symbols by address, the kernel won't be affected by this.
From: Paulo Marques <pmarques@grupopie.com>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
--
Paulo Marques - www.grupopie.com
"There cannot be a crisis today; my schedule is already full."
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1467 bytes --]
--- ./scripts/kallsyms.c.orig 2007-10-30 18:51:28.000000000 +0000
+++ ./scripts/kallsyms.c 2007-10-30 19:07:58.000000000 +0000
@@ -34,7 +34,7 @@
struct sym_entry {
unsigned long long addr;
- unsigned int len;
+ unsigned int len, start_pos;
unsigned char *sym;
};
@@ -202,8 +202,10 @@ static void read_map(FILE *in)
exit (1);
}
}
- if (read_symbol(in, &table[table_cnt]) == 0)
+ if (read_symbol(in, &table[table_cnt]) == 0) {
+ table[table_cnt].start_pos = table_cnt;
table_cnt++;
+ }
}
}
@@ -507,6 +509,35 @@ static void optimize_token_table(void)
}
+static int compare_symbols(const void *a, const void *b)
+{
+ struct sym_entry *sa, *sb;
+ int wa, wb;
+
+ sa = (struct sym_entry *) a;
+ sb = (struct sym_entry *) b;
+
+ // sort by address first
+ if (sa->addr > sb->addr)
+ return 1;
+ if (sa->addr < sb->addr)
+ return -1;
+
+ // sort by "weakness" type
+ wa = (sa->sym[0] == 'w') || (sa->sym[0] == 'W');
+ wb = (sb->sym[0] == 'w') || (sb->sym[0] == 'W');
+ if (wa != wb)
+ return wa - wb;
+
+ // sort by initial order, so that other symbols are left undisturbed
+ return sa->start_pos - sb->start_pos;
+}
+
+static void sort_symbols(void)
+{
+ qsort(table, table_cnt, sizeof(struct sym_entry), compare_symbols);
+}
+
int main(int argc, char **argv)
{
if (argc >= 2) {
@@ -527,6 +558,7 @@ int main(int argc, char **argv)
usage();
read_map(stdin);
+ sort_symbols();
optimize_token_table();
write_src();
next reply other threads:[~2007-12-04 20:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 20:35 Paulo Marques [this message]
2007-12-04 21:14 ` [-mm PATCH] kallsyms should prefer non weak symbols Mathieu Desnoyers
2007-12-05 12:07 ` Paulo Marques
2007-12-04 21:17 ` Andrew Morton
2007-12-04 21:38 ` Mathieu Desnoyers
2007-12-04 21:34 ` Arjan van de Ven
2007-12-04 22:31 ` Mathieu Desnoyers
2007-12-05 9:37 ` Rusty Russell
2007-12-05 2:05 ` Rusty Russell
2007-12-05 3:09 ` Andrew Morton
2007-12-05 3:14 ` Andrew Morton
2007-12-05 5:01 ` Mathieu Desnoyers
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=4755BA14.8060706@grupopie.com \
--to=pmarques@grupopie.com \
--cc=akpm@osdl.org \
--cc=compudj@krystal.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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