On Tue, 21 May 2002, Russell King wrote:
> 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.
Well, the .modinfo section should only be generated for objects build as
modules, not into the kernel. So it very much likes some object has been
compiled with -DMODULE, though it gets linked into the kernel.
(Which one is it? Obviously it has MODULE_PARM(minor/flash_base/size) in
it)
> 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?
Well, discarding .modinfo would only hide errors like this, so I wouldn't
think it's a good idea.
--Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu May 23 2002 - 22:00:21 EST