From: Andi Kleen <ak@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: sys_ioctl export
Date: Thu, 17 Jun 2004 18:54:28 +0000 [thread overview]
Message-ID: <20040617205428.7da56254.ak@suse.de> (raw)
In-Reply-To: <1087494747.28235.28.camel@markh1.pdx.osdl.net>
On Thu, 17 Jun 2004 11:50:36 -0700
David Mosberger <davidm@napali.hpl.hp.com> wrote:
> >>>>> On Thu, 17 Jun 2004 20:42:28 +0200, Andi Kleen <ak@suse.de> said:
>
> >> AFAIK, there is no ia64-specific reason to export the symbol. If
> >> there is a platform-independent reason for doing so, then it
> >> should be exported for all platform, by putting an
> >> EXPORT_SYMBOL() after fs/ioctl.c:sys_ioctl().
>
> Andi> It's needed to write 32bit compat ioctl handlers in modules.
>
> That makes sense.
Only partly to be honest. The module count handling for such modules
is currently quite dubious bordering to broken (it's possible to get it right, but
rather difficult)
> Andi> I would suggest to export it on IA64 too or everywhere.
>
> Why not export it everywhere then? It seems strange to allow it to be
> called from modules on 64-bit platforms but not 32-bit platforms.
Just someone has to submit the patch to do and and remove it from
all the archs.
-Andi
next prev parent reply other threads:[~2004-06-17 18:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 17:52 sys_ioctl export Mark Haverkamp
2004-06-17 18:20 ` Grant Grundler
2004-06-17 18:30 ` David Mosberger
2004-06-17 18:31 ` Mark Haverkamp
2004-06-17 18:42 ` Andi Kleen
2004-06-17 18:50 ` Grant Grundler
2004-06-17 18:50 ` David Mosberger
2004-06-17 18:54 ` Andi Kleen [this message]
2004-06-17 19:27 ` Grant Grundler
2004-06-17 19:36 ` Mark Haverkamp
2004-06-17 21:25 ` David Mosberger
2004-06-18 6:54 ` Christoph Hellwig
2004-06-18 14:32 ` Jesse Barnes
2004-06-18 14:37 ` Christoph Hellwig
2004-06-18 14:44 ` Jesse Barnes
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=20040617205428.7da56254.ak@suse.de \
--to=ak@suse.de \
--cc=linux-ia64@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