From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: markus.lidel@shadowconnect.com, linux-kernel@vger.kernel.org,
Patrick McHardy <kaber@trash.net>,
davem@davemloft.net
Subject: Re: [2.6 patch] drivers/message/i2o/iop.c: static inline functions mustn't be exported
Date: Wed, 19 Apr 2006 10:33:44 +0200 [thread overview]
Message-ID: <20060419083344.GA25047@stusta.de> (raw)
In-Reply-To: <20060418230600.4bccd221.akpm@osdl.org>
On Tue, Apr 18, 2006 at 11:06:00PM -0700, Andrew Morton wrote:
> Adrian Bunk <bunk@stusta.de> wrote:
> >
> > static inline functions mustn't be exported.
> >
>
> Actually, exports of static inlines work OK. The compiler will emit an
> out-of-line copy to satisfy EXPORT_SYMBOL's reference and the module
> namespace is separate from the compiler&linker's namespace.
>
> Of course, things will screw up when we're using the compiler&linker
> namespace (ie: the driver is statically linked).
>...
It even works with statically linked drivers.
It does work unless CONFIG_MODULES=n.
But this doesn't mean it's OK - exporting static code is wrong.
BTW:
It seems Patrick's recently merged patch to let the compiler help us
find such bugs (a1a8feed1743ec8d2af1dafa7c5321679f0a3e4f) isn't working.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-04-19 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 15:06 [2.6 patch] drivers/message/i2o/iop.c: static inline functions mustn't be exported Adrian Bunk
2006-04-19 6:06 ` Andrew Morton
2006-04-19 8:33 ` Adrian Bunk [this message]
2006-04-19 15:59 ` Patrick McHardy
2006-04-20 23:17 ` Markus Lidel
-- strict thread matches above, loose matches on Subject: below --
2006-04-13 16:22 Adrian Bunk
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=20060419083344.GA25047@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.lidel@shadowconnect.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 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.