public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Ole Husgaard <osh@sparre.dk>
Cc: Christoph Hellwig <hch@infradead.org>,
	David Grothe <dave@gcom.com>,
	Petr Vandrovec <VANDROVE@vc.cvut.cz>,
	linux-kernel@vger.kernel.org,
	LiS <linux-streams@gsyc.escet.urjc.es>,
	davem@redhat.com
Subject: Re: [Linux-streams] Re: [PATCH] Re: export of sys_call_tabl
Date: Sat, 12 Oct 2002 03:56:42 -0600	[thread overview]
Message-ID: <20021012035642.B14955@openss7.org> (raw)
In-Reply-To: <3DA78926.FB2299A@sparre.dk>; from osh@sparre.dk on Sat, Oct 12, 2002 at 04:29:58AM +0200

Ole,

I don't think that exporting putpmsg and getpmsg as _GPL will
stop proprietary modules from being linked with LiS.  LiS exports
its symbols on a different basis.  There is no need for a proprietary
module using LiS to access putpmsg or getpmsg or the syscall
registration facility for that matter.  Is you concern that LiS
using a _GPL only facility will force GPL on modules linked with LiS
even though LiS is LGPL?

--brian

On Sat, 12 Oct 2002, Ole Husgaard wrote:

> "Brian F. G. Bidulock" wrote:
> > On Fri, 11 Oct 2002, Christoph Hellwig wrote:
> > > It is not.  Sys_call_table was exported to allow iBCS/Linux-ABI
> > 
> > I don't know if it matters, but these two calls putpmsg and getpmsg
> > are the calls used by iBCS.
> 
> AFAIK, iBCS use these syscalls to emulate TLI, and iBCS
> only has this emulation working for the IP protocol suite.
> 
> LiS is hooking the same syscalls, and is more protocol
> independent.
> 
> In this way, iBCS and LiS are competing projects, even
> if their base objectives are very different (iBCS aims
> for user-level binary portability from SysV, while LiS
> aims for kernel-level STREAMS code portability from SysV
> to extend to Linux).
> 
> > No, I don't think anyone wants proprietary syscalls to be registered
> > with this facility.  If _GPL can allow an LGPL module to use the
> > facility without problems, that will be the best way to go.
> 
> An LGPL module with proprietary code linked into it will
> taint the kernel. LiS is often linked with proprietary
> code, since it is under LGPL.
> 
> IMHO, A not-GPL-only export from the kernel is needed
> here.
> 
> That will not make these syscalls proprietary. Even with
> proprietary drivers linked into LiS, it is impossible to
> deviate from the SysV definition of putpmsg/getpmsg
> unless the code of LiS itself is modified.
> 
> Best Regards,
> 
> Ole Husgaard.

-- 
Brian F. G. Bidulock    ¦ The reasonable man adapts himself to the ¦
bidulock@openss7.org    ¦ world; the unreasonable one persists in  ¦
http://www.openss7.org/ ¦ trying  to adapt the  world  to himself. ¦
                        ¦ Therefore  all  progress  depends on the ¦
                        ¦ unreasonable man. -- George Bernard Shaw ¦

  parent reply	other threads:[~2002-10-12  9:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 16:38 [Linux-streams] Re: [PATCH] Re: export of sys_call_tabl Petr Vandrovec
2002-10-10 16:57 ` David Grothe
2002-10-10 17:27   ` Christoph Hellwig
2002-10-10 19:07     ` David Grothe
2002-10-10 19:33       ` Arjan van de Ven
2002-10-10 20:31       ` David Grothe
     [not found]       ` <20021011180209.A30671@infradead.org>
     [not found]         ` <20021011142657.B32421@openss7.org>
2002-10-12  2:29           ` Ole Husgaard
2002-10-12  9:32             ` Arjan van de Ven
2002-10-12  9:54               ` Brian F. G. Bidulock
2002-10-12  9:56             ` Brian F. G. Bidulock [this message]
2002-10-12 11:51               ` Alan Cox
2002-10-12 15:29               ` Ole Husgaard
  -- strict thread matches above, loose matches on Subject: below --
2002-10-10 19:41 Petr Vandrovec
2002-10-11 14:22 ` David Grothe
2002-10-11 14:49   ` Alan Cox
2002-10-10 16:32 David Grothe
2002-10-10 16:25 Petr Vandrovec
2002-10-10 16:30 ` David Grothe

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=20021012035642.B14955@openss7.org \
    --to=bidulock@openss7.org \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=dave@gcom.com \
    --cc=davem@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-streams@gsyc.escet.urjc.es \
    --cc=osh@sparre.dk \
    /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