Re: Linux GPL and binary module exception clause?

[Kendall Bennett]

viro@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:

> On Wed, Dec 10, 2003 at 11:48:45AM -0800, Kendall Bennett wrote:
> > Linus Torvalds <torvalds@xxxxxxxx> wrote:
> > 
> > > In fact, a user program written in 1991 is actually still likely
> > > to run, if it doesn't do a lot of special things. So user programs
> > > really are a hell of a lot more insulated than kernel modules, which
> > > have been known to break weekly. 
> > 
> > IMHO (and IANAL of course), it seems a bit tenuous to me the argument
> > that just because you deliberating break compatibility at the module
> > level on a regular basis, that they are automatically derived works.
> > Clearly the module interfaces could be stabilised and published, and if
> > you consider the instance of a single kernel version in time, that
> > module ABI *is* published and *is* stable *for that version*. Just
> > because you make an active effort to change things and actively *not*
> > document the ABI other than in the source code across kernel versions,
> > doesn't automatically make a module a derived work. 
> 
> Oh, for crying out loud!  Had you ever looked at that "API"?
> 
> At least 90% of it are random functions exposing random details of
> internals. Most of them are there only because some in-tree piece
> of code had been "modularized".  Badly. 

The fact that an API is 'badly' implemented does not detract from the 
fact that it is an API. It is still published as the mechanism that a 
module would use to load and interface to the kernel, via that API.

> In 2.7 we need to get the export list back to sanity.  Right now it's a
> such a junkpile that speaking about even a relative stability for it... 
> Not funny. 

You miss my point. I was talking about a single kernel version. For a 
single kernel version, the ABI is both *published* and *stable*. Sure it 
may not be what you consider a *clean* or *good* ABI, but it *IS* an ABI. 
Note that:

1. It is a published ABI because for that one kernel release, all the 
source code is available that documents the ABI (albiet badly IYO).

2. It is stable because that kernel version will never change on your 
machine.

Given that it is a stable and published ABI for a single kernel version, 
then what makes a kernel module different from a user program? The fact 
that binary only modules are *only* guaranteed to work with one single 
kernel version, the fact that the ABI changes from version to version is 
completely irrelevant to determing whether a binary module is derived 
from the kernel or not.

Regards,

---
Kendall Bennett
Chief Executive Officer
SciTech Software, Inc.
Phone: (530) 894 8400
http://www.scitechsoft.com

~ SciTech SNAP - The future of device driver technology! ~

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/