All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: OProfile cannot be loaded as module...
Date: Tue, 18 Oct 2005 08:46:20 -0700	[thread overview]
Message-ID: <435518CC.3060403@avtrex.com> (raw)
In-Reply-To: <20051018110355.GB2656@linux-mips.org>

Ralf Baechle wrote:
> On Mon, Oct 17, 2005 at 01:14:01PM -0700, David Daney wrote:

>>Fine, but what exactly are the semantics of __attribute__((weak)) in 
>>modules?  It gets resolved when linking with other objects that make up 
>>the module.  But what if the weak symbol can be resolved at module load 
>>time against symbols in either the kernel proper or other modules?
> 
> 
> Yes.
> 
> 
>>What happens if the weak symbol can be resolved by a symbol in a module
>>that is loaded after the one with the weak symbol?  Does it get fixed up
>>when the new module is loaded?
> 
> 
> No, it won't - and I don't think that would be a good idea.  The potencial
> for bugs is just too large.
> 

Given your 'yes' and 'no' answers, the behavior of a module could depend 
on the order in which the modules are loaded, as they can be linked 
differently depending on which modules are already present.

That doesn't seem like a good way of doing things.

If if were up to me (and I know that it is not), I would disallow 
linking of weak symbols at module load time altogether.

David Daney.

  reply	other threads:[~2005-10-18 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07 23:59 OProfile cannot be loaded as module David Daney
2005-10-08  0:25 ` David Daney
2005-10-13 22:55 ` Ralf Baechle
2005-10-17 20:14   ` David Daney
2005-10-18 11:03     ` Ralf Baechle
2005-10-18 15:46       ` David Daney [this message]
2005-10-18 16:38         ` Ralf Baechle
2006-04-21 14:33   ` Atsushi Nemoto

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=435518CC.3060403@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.