|
|
Log in / Subscribe / Register

Shrinking shrinker locking overhead

Shrinking shrinker locking overhead

Posted Sep 16, 2023 4:50 UTC (Sat) by NYKevin (subscriber, #129325)
In reply to: Shrinking shrinker locking overhead by pizza
Parent article: Shrinking shrinker locking overhead

Not under 17 USC 1202:

> (3) As used in this subsection—
> (A) to “circumvent a technological measure” means to descramble a scrambled work, to decrypt an encrypted work, or otherwise to avoid, bypass, remove, deactivate, or impair a technological measure, without the authority of the copyright owner; and
> (B) a technological measure “effectively controls access to a work” if the measure, in the ordinary course of its operation, requires the application of information, or a process or a treatment, with the authority of the copyright owner, to gain access to the work.

If you don't meet the test in (B), then it's not DRM and there's no 1202 liability. You don't need "the authority of the [kernel's] copyright owner" to mark your own module as GPL'd (and thereby gain access to GPL-only interfaces), so the GPL-only restriction does not effectively control access to the kernel within the meaning of 1202.

1203 is more debatable:

> (a) False Copyright Management Information.—No person shall knowingly and with the intent to induce, enable, facilitate, or conceal infringement—
> (1) provide copyright management information that is false, or
> [...]
> (c) Definition.—As used in this section, the term “copyright management information” means any of the following information [...], except that such term does not include any personally identifying information about a user [...]:
> [...]
> (6) Terms and conditions for use of the work.

So you could argue that, by falsely marking your module as GPL'd, you're violating this law. OTOH, one could make exactly the same argument about the upstream GPL-only marker, as derivative works don't really follow bright line rules like that in the first place. I suspect a US court would at least seriously consider applying the equitable doctrine of unclean hands in such a scenario (i.e. you cannot violate the law, and then sue somebody else for violating the law, when your violation directly caused their violation).

However, there is a far more straightforward defense: If you didn't have "the intent to induce, enable, facilitate, or conceal infringement" (because you honestly believe that your module is not a derivative work), then you don't violate (a) and therefore haven't broken the law at all.


to post comments

Shrinking shrinker locking overhead

Posted Sep 16, 2023 12:32 UTC (Sat) by IanKelling (subscriber, #89418) [Link] (1 responses)

> You don't need "the authority of the [kernel's] copyright owner" to mark your own module as GPL'd

I'm not trying to argue that your larger point is wrong, but this particular sentence in isolation strikes me as very odd because copyright law say you certainly do need the authority of the [kernel's] copyright owner to do things like mark your own module as GPL'd. Perhaps for various reasons that is not the kind of authority it is talking about, including that permission was already irrevocably granted.

Shrinking shrinker locking overhead

Posted Sep 29, 2023 18:48 UTC (Fri) by sammythesnake (guest, #17693) [Link]

> you certainly do need the authority of the [kernel's] copyright owner to do things like mark your own module as GPL'd.

Howso? If the module isn't a derivative work of the kernel, then the copyright ownership of the kernel code is entirely irrelevant. The rights of an author do not extend to others' non-derivative works.

Even if it were, the GPL explicitly disclaims any consideration of how the code is *used* (without distribution) so the copyright holders have already granted permission to lie to the API (to whatever extent that such permission is required , which is none at all in many jurisdictions, but YMMV)

A kernel module (whether derived from kernel code or not) uses an API (which includes a flag indicating "this is GPL code") The API is described in various documentation that you can read without ever seeing the kernel code. If the module's authors never see the kernel code, then it can't be a derivative work of that kernel code.

This is a really important fact of how the GPL and other licences (including proprietary ones) work. They can only grant permission to do things the author is entitled to withhold, not withdraw entitlement the user gets by default. Stuff like parody, journalism, fair use/fair dealing etc. give certain freedoms of use/reuse otherwise covered by copyright, but even those are exceptions for where there is a relevant copyright to consider. That isn't the case if the original work (in this case, we're talking about kernel code) isn't copied/modified/distributed/whatever.

It's very important to remember that the *authors' opinion* of what counts as a derivative work is a distraction - that question is a matter for the legal system (i.e. copyright law, relevant judicial precedent and potentially the vagaries of any courts/juries that might get involved)


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds