From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Subject: 1GB piggys
Date: Tue, 21 May 2002 12:40:57 +0100 [thread overview]
Message-ID: <20020521124057.A2286@flint.arm.linux.org.uk> (raw)
Hi,
I'm getting reports of some people ending up with 1GB piggy objects for
gzip to compress on ARM. While investigating this, I found the following:
00003dd4 ? __module_kernel_version
00003df4 ? __module_parm_minor
00003e04 ? __module_parm_flash_base
00003e18 ? __module_parm_flash_size
40004000 A swapper_pg_dir
40008000 ? __init_begin
40008000 ? _stext
40008000 ? stext
The __module_* stuff is from the .modinfo section of some kernel object.
Since .modinfo isn't actually used or indeed placed in the linker
script, shouldn't we be explicitly discarding it like the
.exitcall.exit, .text.exit and .data.exit sections, rather than
letting the linker apparantly pick some random memory location to
dump this section?
(Yes, its probably buggy for the linker not to moan about unrecognised
input sections...)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next reply other threads:[~2002-05-21 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 11:40 Russell King [this message]
2002-05-21 14:37 ` 1GB piggys Kai Germaschewski
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=20020521124057.A2286@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.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