From: Christoph Hellwig <hch@caldera.de>
To: Mike Jagdis <jaggy@purplet.demon.co.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, arjanv@redhat.com
Subject: Re: [PATCH] syscall exports - against 2.4.14-pre3
Date: Tue, 30 Oct 2001 11:37:31 +0100 [thread overview]
Message-ID: <20011030113731.A14808@caldera.de> (raw)
In-Reply-To: <20011029173711.B24272@caldera.de> <3BDE7D22.8000006@purplet.demon.co.uk>
In-Reply-To: <3BDE7D22.8000006@purplet.demon.co.uk>; from jaggy@purplet.demon.co.uk on Tue, Oct 30, 2001 at 10:12:50AM +0000
On Tue, Oct 30, 2001 at 10:12:50AM +0000, Mike Jagdis wrote:
> Christoph Hellwig wrote:
> > Hi Linus,
> >
> > once again the syscall export patch - back to EXPORT_SYMBOL
> > vs EXPORT_SYMBOL_GPL due to some complaints, more syscalls
> > as I dropped sys_call_table abuse in linux-abi.
>
> The whole *point* of the sys_call_table "abuse" was to avoid having
> the whole damn lot in the export list!
It is not only ugly over belief but also unportable.
For example the mips port does not have a sys_call_table array at all,
on IA64 funktion pointer do _NOT_ fit into an unsigned long so at least
the prototype is wrong if it works at all.
> As a side effect it meant that any module that patched the
> sys_call_table (funky tracers, security hot-fixes, whatever)
> would work seamlessly with non-Linux binaries.
This is not only racy (no locking!) but also a loophole for binary
modules to do all kinds of crap (see http://www.sysinternals.com/linux/
utilities/filemon.shtml for details). In early 2.5 I will submit a patch
to remove the export, let's see wether it will be accepted.
>
> > Could you _please_ apply it - it is badly needed for foreign
> > personalities compiled as modules.
>
> I can't see why? iBCS always was a module for years before
> linux-abi dumped it back in a humungous kernel patch.
"Because we did it all the time it's right".
Of course it worked - that doesn't mean it's a good idea.
Arjan might want to comment on how gcc 2.96+ liked the old concept..
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-10-30 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 16:37 [PATCH] syscall exports - against 2.4.14-pre3 Christoph Hellwig
2001-10-30 10:12 ` Mike Jagdis
2001-10-30 10:37 ` Christoph Hellwig [this message]
2001-10-30 10:44 ` Arjan van de Ven
2001-10-30 15:15 ` John Levon
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=20011030113731.A14808@caldera.de \
--to=hch@caldera.de \
--cc=arjanv@redhat.com \
--cc=jaggy@purplet.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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.