Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Thibaut VARENE <varenet@gmail.com>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Module Relocation Problem
Date: Wed, 14 Jun 2006 16:02:10 +0800	[thread overview]
Message-ID: <448FC282.80402@tausq.org> (raw)
In-Reply-To: <7d01f9f00606060551n2aabd3e9p908745991df33a2f@mail.gmail.com>

> A number of kernel modules fail to load nowadays on parisc. That
> includes xfs, netfilter, ipv6... Some are known bloated big ones, but
> others are quite surprising. In any case that's clearly a problem we
> want to fix at some point.
> 
> I remember Randolph saying that might indeed be a kernel loader
> issue... Randolph, any thought?

ok, several things:

- I looked at fixing this in binutils, which is really the "right" place
to fix this; unfortunately the changes required are very extensive, so I
gave up

- I looked at using -mlong-calls to address this issue. I've added the
missing relocation that was reported in a previous message on this
thread, but there are other problems - with modules compiled with
-mlong-call I am seeing rather bizarre crashes that I have not had time
to debug further. I do not yet know why they are happening, although I
suspect it has to do with bve clobbering r31. I'm not yet sure if this
is a kernel problem or a gcc problem.

- As to "small" modules causing the out of bounds problem - I haven't
really looked at any modules other than ipv6. If there's a particular
one that is "surprising", I can take a look. Usually it's quite obvious
where the out of bounds problem is.

- As an aside, while looking at the module loading problem, I've
convinced myself that the 64-bit module loader is wrong. OTOH, it seems
to work in most cases, so there's clearly something that I don't yet
understand.....

The module loader has a hard coded limit for the number of GOT entries.
We can exceed this rather easily in some cases when we are using long calls.

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2006-06-14  8:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06  1:45 [parisc-linux] Module Relocation Problem Kai Holthaus
2006-06-06  2:20 ` John David Anglin
2006-06-06  2:26   ` John David Anglin
2006-06-06  2:38   ` Kai Holthaus
2006-06-06  3:07     ` John David Anglin
2006-06-06  3:20       ` Kai Holthaus
2006-06-06  3:49         ` John David Anglin
2006-06-06 12:51           ` Thibaut VARENE
2006-06-14  8:02             ` Randolph Chung [this message]
2006-06-14 16:47               ` James Bottomley
     [not found] <J0FGHF$3C34E7AFFFACE857F314B50EFB7BB29D@scarlet.be>
     [not found] ` <200606101105.38472.kmh@sonic.net>
     [not found]   ` <448B184F.7020309@tiscali.be>
2006-06-26  2:02     ` Kai Holthaus
2006-06-26  2:10       ` Kyle McMartin
     [not found]         ` <200606252124.58264.kmh@sonic.net>
2006-06-26 12:10           ` Kyle McMartin

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=448FC282.80402@tausq.org \
    --to=randolph@tausq.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=varenet@gmail.com \
    /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