Re: The disappearing sys_call_table export.

[Yoav Weiss]

> You might have a derivative work after obtaining access to a
> non-exported interface.  If this is correct, binary-only modules
> can't do this and therefore they must stick to exported interfaces.

Thats an interesting question.  Who violates the license here ?  It can't
be the author of the binary driver (unless it was in breach before the
symbol was unexported).  Thats because it didn't change.  The user,
wishing to keep using his driver although the kernel changed and broke it,
generates and insmod's a module that re-exports a symbol that the module
relies upon.  However, the user didn't release any code so he can't be in
breach either.

Its just a method backwards compatibility of kernel modules.  Of course,
IANAL, so I may be wrong here.

One could argue that the binary module was in breach in the first place,
because of various reasons.  My point is that the re-exporting module
didn't change anything in terms of derived work.

	Yoav Weiss