From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Richard Earnshaw <Richard.Earnshaw@arm.com>
Cc: linux-kernel@vger.kernel.org,
Catalin Marinas <Catalin.Marinas@arm.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [RFC] ARM binutils feature churn causing kernel problems
Date: Tue, 5 Oct 2004 14:14:52 +0100 [thread overview]
Message-ID: <20041005141452.B6910@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1096981035.14574.20.camel@pc960.cambridge.arm.com>; from Richard.Earnshaw@arm.com on Tue, Oct 05, 2004 at 01:57:15PM +0100
On Tue, Oct 05, 2004 at 01:57:15PM +0100, Richard Earnshaw wrote:
> On Tue, 2004-10-05 at 12:53, Russell King wrote:
> > diff -up -x BitKeeper -x ChangeSet -x SCCS -x _xlk -x *.orig -x *.rej orig/scripts/kallsyms.c linux/scripts/kallsyms.c
> > --- orig/scripts/kallsyms.c Sun Jul 11 22:56:39 2004
> > +++ linux/scripts/kallsyms.c Tue Oct 5 12:51:26 2004
> > @@ -32,6 +32,17 @@ usage(void)
> > exit(1);
> > }
> >
> > +/*
> > + * This ignores the intensely annoying "mapping symbols" found
> > + * in ARM ELF files: $a, $t and $d.
> > + */
> > +static inline int
> > +is_arm_mapping_symbol(const char *str)
> > +{
> > + return str[0] == '$' && strchr("atd", str[1]) &&
> > + (str[2] == '\0' || str[2] == '.');
> > +}
> > +
> > static int
> > read_symbol(FILE *in, struct sym_entry *s)
> > {
> > @@ -56,7 +67,8 @@ read_symbol(FILE *in, struct sym_entry *
> > _sinittext = s->addr;
> > else if (strcmp(str, "_einittext") == 0)
> > _einittext = s->addr;
> > - else if (toupper(s->type) == 'A' || toupper(s->type) == 'U')
> > + else if (toupper(s->type) == 'A' || toupper(s->type) == 'U' ||
> > + is_arm_mapping_symbol(str))
> > return -1;
> >
> > s->sym = strdup(str);
>
> Why don't you pass s to is_arm_mapping_symbol and have it do the same
> thing as you've done in get_ksymbol?
"sym_entry" is not an ELF symtab structure - it's a parsed version
of the `nm' output, and as such does not contain the symbol type nor
binding information.
> ----------------------------------------------------------------
> This e-mail message is intended for the addressee(s) only and may
> contain information that is the property of, and/or subject to a
> confidentiality agreement between the intended recipient(s), their
> organisation and/or the ARM Group of Companies. If you are not an
> intended recipient of this e-mail message, you should not read, copy,
> forward or otherwise distribute or further disclose the information in
> it; misuse of the contents of this e-mail message may violate various
> laws in your state, country or jurisdiction. If you have received this
> e-mail message in error, please contact the originator of this e-mail
> message via e-mail and delete all copies of this message from your
> computer or network, thank you.
> ----------------------------------------------------------------
Does this apply to your message? It would appear that third parties
subscribed to linux-kernel are not allowed to read your messages
because they're not an "intended recipient" !
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-10-05 13:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 20:03 Russell King
2004-09-27 20:17 ` Christoph Hellwig
2004-09-27 20:35 ` Russell King
2004-09-27 20:37 ` Nicolas Pitre
2004-10-01 20:11 ` Russell King
2004-10-04 12:01 ` Catalin Marinas
2004-10-04 23:18 ` Rusty Russell
2004-10-05 11:10 ` Richard Earnshaw
2004-10-05 11:53 ` Russell King
2004-10-05 12:57 ` Richard Earnshaw
2004-10-05 13:14 ` Russell King [this message]
2004-10-05 13:40 ` Richard Earnshaw
2004-10-05 13:51 ` Russell King
2004-10-06 10:08 ` Adrian Cox
2004-10-07 15:02 ` Russell King
2004-10-12 13:15 ` Richard Earnshaw
2004-10-07 14:54 ` Russell King
2004-10-05 23:00 ` Rusty Russell
2004-10-07 12:35 ` Paulo Marques
2004-10-07 15:01 ` Russell King
2004-10-07 16:39 ` Paulo Marques
2004-10-05 13:02 ` Richard Earnshaw
2004-10-08 15:04 ` Russell King
2004-10-08 16:36 ` Paulo Marques
2004-10-08 18:14 ` Albert Cahalan
2004-10-08 19:43 ` Paulo Marques
2004-10-20 11:38 ` [PATCH] Fix ARM kernel build with permitted binutils versions Russell King
2004-10-26 22:37 ` Sam Ravnborg
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=20041005141452.B6910@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=Catalin.Marinas@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.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
Powered by JetHome