linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] dynamic syscalls revisited
Date: Mon, 6 Dec 2004 00:46:05 +0100	[thread overview]
Message-ID: <20041205234605.GF2953@stusta.de> (raw)
In-Reply-To: <1101748258.25841.53.camel@localhost.localdomain>

On Mon, Nov 29, 2004 at 12:10:58PM -0500, Steven Rostedt wrote:
> On Mon, 2004-11-29 at 17:41 +0100, Jan Engelhardt wrote:
> > I do not see how dsyscalls could be better than static ones, so they are
> > one-on-one. Maybe someone could elaborate why they are "a really bad idea"?
> 
> The one argument against them, that I agree with, is Linus' hooks to
> avoid the GPL.  A binary only module could easily add their own hooks
> into the kernel.
> 
> I've made this patch with the option to turn this off. I should have put
> the option in Kernel debugging with the default off (the default is
> currently on so that if you apply the patch, you have it automatically).
> This way binary only modules can't take advantage of the dynamic
> syscalls without recompiling the kernel.  If the user needed to compile
> the kernel, then a patch can easily be added, so this is just as good of
> a defense. 

Why don't you EXPORT_SYMBOL_GPL dsyscall_{,un}register?

This should at least fix the binary only module concerns.

> -- Steve

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


  reply	other threads:[~2004-12-05 23:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-29 15:11 [PATCH][RFC] dynamic syscalls revisited Steven Rostedt
2004-11-29 15:17 ` Christoph Hellwig
2004-11-29 15:36   ` Steven Rostedt
2004-11-30 19:30     ` Kristian Sørensen
2004-11-29 16:41   ` [RFC] " Jan Engelhardt
2004-11-29 17:10     ` Steven Rostedt
2004-12-05 23:46       ` Adrian Bunk [this message]
2004-12-06 16:07         ` Steven Rostedt
2004-12-06 17:16           ` Steven Rostedt
2004-12-06 17:32             ` Zwane Mwaikambo
2004-12-06 17:57               ` linux-os
2004-12-06 18:03               ` Steven Rostedt
2004-12-06 18:18               ` Arjan van de Ven
2004-12-07  0:20           ` Michael Buesch
2004-12-07  0:57             ` Steven Rostedt
2004-12-06 21:14     ` H. Peter Anvin
2004-12-06 22:01       ` Steven Rostedt
2004-12-06 22:20         ` H. Peter Anvin
2004-12-06 22:38           ` Steven Rostedt
2004-12-14 23:14             ` Werner Almesberger
2004-12-15  2:14               ` Steven Rostedt
2004-12-15  3:35                 ` Steven Rostedt

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=20041205234605.GF2953@stusta.de \
    --to=bunk@stusta.de \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).