Re: [1/1] connector: Kernel connector - userspace <-> kernelspace "linker".

Luis R. Rodriguez
2004-09-24T06:57:56Z

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

On Fri, Sep 24, 2004 at 02:32:31AM -0400, Luis R. Rodriguez wrote:
> On Fri, Sep 24, 2004 at 10:30:04AM +0400, Evgeniy Polyakov wrote:
> >
> > BTW, it can also restrict userspace event notification in following way:
> > when someone sends a message to notify group A of
> > registering/unregistering of device with id {x,y} then connector can
> > check if this group A is registered through callback_register_gpl(it is
> > not exist for now, but can be created as a copy of callback_register() )
> > or not. If it is GPL - send notify, else - execute
> > "mail -s "shit happens" linux-kernel@vger.kernel.org"
> > in the way /sbin/hotplug is called.
> > BTW, this decision also can be obtained from external policy module.
> >
> > As you may think connector in current implementation is quite powerful
> > interface( if I will not praise it, who will? :) ), and somebody can
> > make bad things a bit easier with it, but it is also very flexible and
> > can be tuned to suit your needs.
> >
> > I'm open for discussion :)
>
> Kernel maintainers:
>
> What do you think? Can a driver which requires access to binary
> callbacks be included as part of the stock kernel as GPL if Evgeniy's
> Connector provides some sort of kernel "jail" for the callback
> functionality?
>
> Luis
>

BTW just wanted to say I realize all this is rediculous, I'm just
testing waters ;)

Luis

--
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84 A34A 6ADD 4937 E20A 525E

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]