From: ebiederm@xmission•com (Eric W. Biederman)
To: David Laight <David.Laight@ACULAB•COM>
Cc: 'Chris Leech' <cleech@redhat•com>,
"netdev\@vger.kernel.org" <netdev@vger•kernel.org>,
"containers\@lists.linux-foundation.org"
<containers@lists•linux-foundation.org>
Subject: Re: [PATCH 0/9] use network namespace for iSCSI control interfaces
Date: Tue, 21 Nov 2017 13:46:03 -0600 [thread overview]
Message-ID: <87mv3fo1ok.fsf@xmission.com> (raw)
In-Reply-To: <687d0196888f4325aebc0989a8e12ced@AcuMS.aculab.com> (David Laight's message of "Tue, 21 Nov 2017 11:26:09 +0000")
David Laight <David.Laight@ACULAB•COM> writes:
> To make matters even more annoying the functions for holding and
> releasing a namespace are GPL_ONLY :-(
I am going to pick on this by itself for a moment without mentioning
anything else, so as hopefully not to derail what otherwise sounds
like a good technical conversation.
So far every time when someone has complained to me about things being
GPL_ONLY and I have looked into it, all I have seen is someone trying
to come up with a way to release derivative works of the kernel without
honoring the terms of the GPLv2.
I read through the US Code a while back to see if I could understand
what is legaly defined as a derivative work, and my impression at the
time was that the FSF is quite conservative in what they consider a
derivative work, and probably the scope is much wider.
So when people start complaining about things being GPLv2 those are the
most annoying bug reports I ever deal with, as almost invariably people
just want to take from the community and don't want to work with every
one else.
It is especially annoying because I have never seen a case where there
is a good justification for a kernel export being anything other than
GPL_ONLY. That is the kernel's license after all, and if you are using
kernel internal functions the chance that your code is not a derivative
work is about 0.
Eric
next prev parent reply other threads:[~2017-11-21 19:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171107180156.GD29597@straylight.hirudinean.org>
[not found] ` <20171107180156.GD29597-r8IHplWLGbA5tHQWs+pTeqPFFGjUI2lm2LY78lusg7I@public.gmane.org>
2017-11-07 22:45 ` [PATCH 0/9] use network namespace for iSCSI control interfaces Chris Leech
2017-11-07 22:45 ` [PATCH 2/9] iscsi: associate endpoints with a host Chris Leech
2017-11-07 22:45 ` [PATCH 3/9] iscsi: sysfs filtering by network namespace Chris Leech
[not found] ` <20171107224513.4217-1-cleech-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-07 22:45 ` [PATCH 1/9] iscsi: create per-net iscsi netlink kernel sockets Chris Leech
2017-11-07 22:45 ` [PATCH 4/9] iscsi: make all iSCSI netlink multicast namespace aware Chris Leech
2017-11-08 10:31 ` [PATCH 0/9] use network namespace for iSCSI control interfaces David Laight
2017-11-15 0:25 ` Chris Leech
2017-11-21 11:26 ` David Laight
2017-11-21 19:46 ` Eric W. Biederman [this message]
[not found] ` <687d0196888f4325aebc0989a8e12ced-1XygrNkDbNvwg4NCKwmqgw@public.gmane.org>
2017-11-21 20:20 ` Chris Leech
2017-11-07 22:45 ` [PATCH 5/9] iscsi: set netns for iscsi_tcp hosts Chris Leech
2017-11-07 22:45 ` [PATCH 6/9] iscsi: check net namespace for all iscsi lookups Chris Leech
2017-11-07 22:45 ` [PATCH 7/9] iscsi: convert flashnode devices from bus to class Chris Leech
2017-11-07 22:45 ` [PATCH 8/9] iscsi: rename iscsi_bus_flash_* to iscsi_flash_* Chris Leech
2017-11-07 22:45 ` [PATCH 9/9] iscsi: filter flashnode sysfs by net namespace Chris Leech
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv3fo1ok.fsf@xmission.com \
--to=ebiederm@xmission$(echo .)com \
--cc=David.Laight@ACULAB$(echo .)COM \
--cc=cleech@redhat$(echo .)com \
--cc=containers@lists$(echo .)linux-foundation.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox