From: Russell King <rmk@arm.linux.org.uk>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: kai@tp1.ruhr-uni-bochum.de, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.59 vmlinux.lds.S change broke modules
Date: Fri, 17 Jan 2003 13:56:38 +0000 [thread overview]
Message-ID: <20030117135638.A376@flint.arm.linux.org.uk> (raw)
In-Reply-To: <15911.64825.624251.707026@harpo.it.uu.se>; from mikpe@csd.uu.se on Fri, Jan 17, 2003 at 01:55:21PM +0100
On Fri, Jan 17, 2003 at 01:55:21PM +0100, Mikael Pettersson wrote:
> This oops occurs for every module, not just af_packet.ko, at
> resolve_symbol()'s first call to __find_symbol().
>
> What happens is that __find_symbol() oopses because the kernel's
> symbol table is in la-la land. (Note the bogus kernel adress
> 2220c021 it tried to dereference above.)
>
> Reverting 2.5.59's patch to arch/i386/vmlinux.lds.S cured the
> problem and modules now load correctly for me.
>
> I don't know if this is a problem also for non-i386 archs.
Well:
__start___ksymtab = .; \
__ksymtab : AT(ADDR(__ksymtab) - LOAD_OFFSET) { \
*(__ksymtab) \
} \
__stop___ksymtab = .; \
breaks on some ARM binutils (from a couple of years ago.) The most
reliable way we've found in with ARM binutils is to place the symbols
inside the section - this appears to work 100% every single time and
I've never had any reports of failure (whereas I did with the symbols
outside as above.)
On the topic of these changes, I'd prefer it if people didn't silently
run around making random stuff generic when there are subtle differences
between each architecture version without:
1. querying why things are different.
2. waiting a reasonable time for replies to why things are different.
3. copying such changes to the architecture maintainers for review
in case steps 1 and 2 failed.
Unfortunately, it seems that the BK disease is growing and seems to
be killing the review process, as some people here predicted it
would. ;(
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-01-17 13:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 12:55 2.5.59 vmlinux.lds.S change broke modules Mikael Pettersson
2003-01-17 13:44 ` Brian Gerst
2003-01-17 13:49 ` Mikael Pettersson
2003-01-17 14:32 ` Mike Galbraith
2003-01-17 13:56 ` Russell King [this message]
2003-01-17 16:13 ` Eric W. Biederman
2003-01-17 16:21 ` Sam Ravnborg
2003-01-18 3:08 ` Eric W. Biederman
2003-01-17 16:24 ` Kai Germaschewski
2003-01-17 16:50 ` Russell King
2003-01-17 16:19 ` Sam Ravnborg
2003-01-17 14:44 ` Kai Germaschewski
2003-01-18 0:11 ` Kai Germaschewski
2003-01-18 5:45 ` Christopher Faylor
2003-01-18 6:14 ` J Sloan
2003-01-18 8:00 ` Mike Galbraith
2003-01-18 9:23 ` Sam Ravnborg
2003-01-18 9:34 ` Mike Galbraith
[not found] ` <Pine.LNX.4.44.0301171808010.15056-100000@chaos.physics.uio wa.edu>
2003-01-18 9:07 ` Mike Galbraith
-- strict thread matches above, loose matches on Subject: below --
2003-01-17 13:27 Adam J. Richter
2003-01-18 14:36 Mikael Pettersson
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=20030117135638.A376@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--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