Re: Binary only module overview

[Eric W. Biederman]

Dave McCracken <[e-mail]> writes:

> --On Monday, September 24, 2001 19:52:13 +0000 Petr Vandrovec
> <[e-mail]> wrote:
> 
> >> > Yes, but the modules are not binary-only.
> >> > The sourcecode is in the package, although it is not GPL.
> >>
> >> I believe they only provide source for an interface layer that can be
> >> compiled against a specific version of the kernel.  I think the core
> >> drivers are binary only.
> >
> > VMnet and VMppuser drivers are completely standalone and can work
> > without VMware. You can persuade VMmon module to load and execute
> > arbitrary code on kernel level - it just provides virtual machine
> > environment (switches CPU context), but as it even does not link to
> > anything else, I do not see any problem here. DRI drivers also allows
> > you to smash arbitrary piece of memory...

Providing an interface to run arbitrary code in kernel space is definentily
against kernel policy.  As adding syscalls from modules have long been
officially off limits.  If the DRI code allows you to smash arbitrary pieces
of memory it probably needs a few checks.  DRI should be an interface
layer that makes it as safe as possible to directly access the video
card from user space.

> >
> > As for license on these modules - I was under impression that they are
> > under GPL, but I'll ask VMware for clarification.
> 
> As a couple of people pointed out privately to me, I was mistaken.  VMware does
> include the complete source to its drivers.

VMmon where it basically allows you to run arbitrary code at the kernel level
does appear to be complete source to me.  Complete source to an interface
layer yes, but not complete source.

> A quick check of the file headers shows a VMware copyright with no mention of
> GPL.  Granted, that's not definitive, but it's a data point.

Well whatever is loaded with VMmon counts as a binary only kernel module.

Eric