* kernel modules, derived work and GPLv2
@ 2023-07-12 14:56 Phil Perry
2023-07-12 15:06 ` Greg KH
2023-07-12 15:58 ` Ezra Buehler
0 siblings, 2 replies; 3+ messages in thread
From: Phil Perry @ 2023-07-12 14:56 UTC (permalink / raw)
To: kernelnewbies; +Cc: torvalds
Hello list,
I am seeking to fully understand my obligations under the GPL regarding
kernel modules, derived works and requirements to distribute the source
code.
If I build a kernel module (driver) against the linux kernel, and that
kernel module is deemed to be a derived work, I understand that it must
also be licensed under the GPL. As such, if I distribute the binary
kernel module (driver), I must also distribute the kernel module source
code. That all seems straightforward, no issues there.
However, what about the source code for the linux kernel the kernel
module (driver) was built against - is that also deemed part of the
derived work and must I also distribute the linux kernel source code
against which my binary kernel module (driver) was compiled?
If yes, what part of the linux kernel source code tree must I
distribute? All of it, or just the source code for the interfaces
(exported symbols) I have used in my module?
If my question is not appropriate for this list, I will happily accept
pointers to a more appropriate forum.
Thanks,
Phil
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: kernel modules, derived work and GPLv2
2023-07-12 14:56 kernel modules, derived work and GPLv2 Phil Perry
@ 2023-07-12 15:06 ` Greg KH
2023-07-12 15:58 ` Ezra Buehler
1 sibling, 0 replies; 3+ messages in thread
From: Greg KH @ 2023-07-12 15:06 UTC (permalink / raw)
To: Phil Perry; +Cc: torvalds, kernelnewbies
On Wed, Jul 12, 2023 at 03:56:40PM +0100, Phil Perry wrote:
> Hello list,
>
> I am seeking to fully understand my obligations under the GPL regarding
> kernel modules, derived works and requirements to distribute the source
> code.
Wonderful. Please contact a lawyer about this if you have questions
about this type of thing, as they are the only ones that can give you
legal advice.
Best of luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: kernel modules, derived work and GPLv2
2023-07-12 14:56 kernel modules, derived work and GPLv2 Phil Perry
2023-07-12 15:06 ` Greg KH
@ 2023-07-12 15:58 ` Ezra Buehler
1 sibling, 0 replies; 3+ messages in thread
From: Ezra Buehler @ 2023-07-12 15:58 UTC (permalink / raw)
To: Phil Perry; +Cc: kernelnewbies
Hi Phil,
On Wed, Jul 12, 2023 at 5:01 PM Phil Perry <phil@elrepo.org> wrote:
> However, what about the source code for the linux kernel the kernel
> module (driver) was built against - is that also deemed part of the
> derived work and must I also distribute the linux kernel source code
> against which my binary kernel module (driver) was compiled?
Perhaps this will answer some questions:
https://www.fsf.org/bulletin/2020/fall/why-providing-source-code-for-unmodified-works-is-important
Cheers,
Ezra
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-07-12 15:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-07-12 14:56 kernel modules, derived work and GPLv2 Phil Perry
2023-07-12 15:06 ` Greg KH
2023-07-12 15:58 ` Ezra Buehler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox