From: Andrea Arcangeli <andrea@suse.de>
To: "Eric S. Raymond" <esr@snark.thyrsus.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Controversy over dynamic linking -- how to end the panic
Date: Fri, 22 Jun 2001 03:29:18 +0200 [thread overview]
Message-ID: <20010622032918.H707@athlon.random> (raw)
In-Reply-To: <200106211814.f5LIEgK04880@snark.thyrsus.com>
In-Reply-To: <200106211814.f5LIEgK04880@snark.thyrsus.com>; from esr@snark.thyrsus.com on Thu, Jun 21, 2001 at 02:14:42PM -0400
> 1. Userland programs which request kernel services via normal system
^^^^^^
> calls *are not* to be considered derivative works of the kernel.
Please, at least don't say "normal" or it will be non obvious that it is
ok for the vsyscalls too (which aren't *that* normal system calls). I'd
rather use "via any kind of official system call (vsyscalls included)".
Otherwise I guess a malicious could try to say that the vsyscalls are
basically dynamically linking the userspace with the kernel (dynamically
linking GPL code in the kernel to whatever non GPL userspace).
vsyscalls cannot give any advantage to the dark side (satellite is
flooding me with the star wars movies sorry ;) anything you can do with
a vsyscall, you can do with a real syscall too, just slower. They can
only improve performance when it is possible to provide the same
functionality without entering/exiting kernel. So nobody sane could ever
complain about the vsyscalls but since you're writing that stuff it
worth to make it explicit I think ;).
Thanks,
Andrea
next prev parent reply other threads:[~2001-06-22 1:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 18:14 Controversy over dynamic linking -- how to end the panic Eric S. Raymond
2001-06-21 18:30 ` Alan Cox
2001-06-21 19:17 ` Eric S. Raymond
2001-06-21 19:51 ` Andrew Pimlott
2001-06-21 20:13 ` Eric S. Raymond
2001-06-21 20:17 ` David S. Miller
2001-06-21 20:46 ` Andrew Pimlott
2001-06-21 21:02 ` Timur Tabi
2001-06-21 21:05 ` Andrew Pimlott
2001-06-21 21:17 ` Timur Tabi
2001-06-21 20:29 ` Timur Tabi
2001-06-21 18:39 ` Jeff Golds
2001-06-21 18:51 ` Jeff Mahoney
2001-06-21 20:02 ` Steve Brueggeman
2001-06-21 18:46 ` Timur Tabi
2001-06-21 19:03 ` Timur Tabi
2001-06-21 19:53 ` Erik Mouw
2001-06-21 19:04 ` Mike Harrold
2001-06-21 19:14 ` Alan Cox
2001-06-21 20:12 ` Marco Colombo
2001-06-21 21:14 ` Alan Cox
2001-06-21 20:31 ` Timur Tabi
2001-06-21 19:08 ` Timur Tabi
2001-06-21 19:17 ` Alexander Viro
2001-06-21 20:01 ` Wei Weng
2001-06-21 19:06 ` Alan Cox
2001-06-21 19:34 ` Jonathan Lundell
2001-06-21 20:17 ` D. Stimits
2001-06-22 11:32 ` Rob Landley
2001-06-21 20:34 ` Craig Milo Rogers
2001-06-21 21:35 ` Controversy over dynamic linking -- how to end the panic (long) Alex Bligh - linux-kernel
2001-06-22 12:32 ` Fair Use (Was Re: Controversy over dynamic linking -- how to end the panic) Rob Landley
2001-06-22 1:29 ` Andrea Arcangeli [this message]
2001-06-22 10:44 ` Controversy over dynamic linking -- how to end the panic David Woodhouse
2001-06-23 20:11 ` Fabrice Gautier
-- strict thread matches above, loose matches on Subject: below --
2001-06-21 19:22 Disconnect
2001-06-21 19:24 ` Alan Cox
2001-06-21 19:25 Jesse Pollard
2001-06-21 21:43 Timur Tabi
2001-06-22 3:05 Rick Hohensee
2001-06-22 4:05 ` kumon
2001-06-23 22:29 ` Scott Wood
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=20010622032918.H707@athlon.random \
--to=andrea@suse.de \
--cc=esr@snark.thyrsus.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox