From: Jason Baietto <jason.baietto@ccur.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: x86_64 module loader reloc problem
Date: Wed, 29 Oct 2003 14:18:22 -0500 [thread overview]
Message-ID: <1067455102.444.18.camel@broccoli> (raw)
Using test8 I'm only able to load kernel modules on x86_64 systems if I
comment out the overflow check for R_X86_64_32 relocation entries in
arch/x64_64/kernel/module.c.
With the check in place I get errors like this:
overflow in relocation type 10 val ffffff0000426b88" errors
`test' likely not compiled with -mcmodel=kernel
insmod: error inserting 'test.ko': -1 Invalid module format
Yes, I'm using -mcmodel=kernel. I'm also using module-init-tools
0.9.15-pre2. Once loaded, the modules appear to be working properly,
but it wouldn't surprise me if a time bomb was lurking there.
What am I doing wrong? Compiler used for both kernel and modules is gcc
(GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-20).
Note that in my linked test module, objdump shows 632 R_X86_64_32 reloc
entries and only 18 R_X86_64_64 reloc entries.
Take care,
Jason
next reply other threads:[~2003-10-29 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 19:18 Jason Baietto [this message]
[not found] <1067455102.444.18.camel@broccoli.suse.lists.linux.kernel>
2003-10-29 19:36 ` x86_64 module loader reloc problem Andi Kleen
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=1067455102.444.18.camel@broccoli \
--to=jason.baietto@ccur.com \
--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;
as well as URLs for NNTP newsgroup(s).