From: Keith Owens <kaos@ocs.com.au>
To: Tom Holroyd <tomh@po.crl.go.jp>
Cc: marcelo@conectiva.com.br,
kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Extraversion in System.map?
Date: Mon, 08 Apr 2002 16:36:56 +1000 [thread overview]
Message-ID: <595.1018247816@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 08 Apr 2002 15:29:47 +0900." <Pine.LNX.4.44.0204081526200.548-100000@holly.crl.go.jp>
On Mon, 8 Apr 2002 15:29:47 +0900 (JST),
Tom Holroyd <tomh@po.crl.go.jp> wrote:
>On Mon, 8 Apr 2002, Keith Owens wrote:
>
>> System.map only contains the numeric kernel version. After all, it is
>> difficult to convert 2.4.19-pre6 to Version_132115-pre6 when symbols
>> cannot contain '-'.
>
>Well, that has an obvious solution, but modifying the Version string
>would likely break something. Adding another string would work. It
>could even be done without making the kernel image bigger. In fact,
>the Version_* symbol (and Extraversion_* symbol) could both be made
>__initdata, couldn't they?
Where the symbol's content is placed is irrelevant. System.map
contains the symbol _name_, not its _contents_. But symbol names
cannot contain the special characters that people put in extraversion.
Even mapping the special characters to '_' will not help because a lot
of people do not change extraversion when changing config and the
change of config can really move symbols around. Hence all the checks
that ksymoops does to validate symbol addresses between multiple
sources.
I have some ideas about making System.map and the kernel record which
build they refer to, including the .config data. But that is 2.5
material, after kbuild 2.5 goes in.
prev parent reply other threads:[~2002-04-08 6:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020405060509.GB30807@holomorphy.com>
2002-04-08 6:07 ` Extraversion in System.map? Tom Holroyd
2002-04-08 6:15 ` Robert Love
2002-04-08 9:41 ` Miquel van Smoorenburg
2002-04-08 6:18 ` Keith Owens
2002-04-08 6:29 ` Tom Holroyd
2002-04-08 6:36 ` Keith Owens [this message]
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=595.1018247816@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=tomh@po.crl.go.jp \
/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