From: Daniel Gomez <da.gomez@samsung.com>
To: "Uwe Kleine-König" <ukleinek@kernel.org>,
"Luis Chamberlain" <mcgrof@kernel.org>
Cc: Werner Sembach <wse@tuxedocomputers.com>,
<tux@tuxedocomputers.com>, Petr Pavlu <petr.pavlu@suse.com>,
Sami Tolvanen <samitolvanen@google.com>,
<linux-modules@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Thorsten Leemhuis <linux@leemhuis.info>
Subject: Re: [PATCH 0/2] module: Block modules by Tuxedo from accessing GPL symbols
Date: Thu, 14 Nov 2024 12:50:15 +0100 [thread overview]
Message-ID: <D5LVNQFINITS.13C3C5UV89XRR@samsung.com> (raw)
In-Reply-To: <20241114103133.547032-4-ukleinek@kernel.org>
On Thu Nov 14, 2024 at 11:31 AM CET, Uwe Kleine-König wrote:
> Hello,
>
> the kernel modules provided by Tuxedo on
> https://protect2.fireeye.com/v1/url?k=2f239e82-70bfb7a8-2f2215cd-000babe598f7-32952349600b722d&q=1&e=9535a8fa-5a9d-4d94-a12d-ff39b9d3b9cf&u=https%3A%2F%2Fgitlab.com%2Ftuxedocomputers%2Fdevelopment%2Fpackages%2Ftuxedo-drivers
> are licensed under GPLv3 or later. This is incompatible with the
> kernel's license and so makes it impossible for distributions and other
> third parties to support these at least in pre-compiled form and so
> limits user experience and the possibilities to work on mainlining these
> drivers.
>
> This incompatibility is created on purpose to control the upstream
> process. See https://protect2.fireeye.com/v1/url?k=12fa0a06-4d66232c-12fb8149-000babe598f7-5be6d19feac11441&q=1&e=9535a8fa-5a9d-4d94-a12d-ff39b9d3b9cf&u=https%3A%2F%2Ffosstodon.org%2F%40kernellogger%2F113423314337991594 for
> a nice summary of the situation and some further links about the issue.
>
> Note that the pull request that fixed the MODULE_LICENSE invocations to
> stop claiming GPL(v2) compatibility was accepted and then immediately
> reverted "for the time being until the legal stuff is sorted out"
> (https://protect2.fireeye.com/v1/url?k=80a9845b-df35ad71-80a80f14-000babe598f7-b5ddbbaedbccb553&q=1&e=9535a8fa-5a9d-4d94-a12d-ff39b9d3b9cf&u=https%3A%2F%2Fgitlab.com%2Ftuxedocomputers%2Fdevelopment%2Fpackages%2Ftuxedo-drivers%2F-%2Fcommit%2Fa8c09b6c2ce6393fe39d8652d133af9f06cfb427).
This commit did not remove the license boilerplate as this other one [1]
upstream did. So I think the license was still inconsistent.
[1] 1a59d1b8e05ea6ab45f7e18897de1ef0e6bc3da6 ("treewide: Replace GPLv2
boilerplate/reference with SPDX - rule 15").
>
> Best regards
> Uwe
>
> Uwe Kleine-König (2):
> module: Put known GPL offenders in an array
> module: Block modules by Tuxedo from accessing GPL symbols
>
> kernel/module/main.c | 56 +++++++++++++++++++++++++++++++++++++-------
> 1 file changed, 47 insertions(+), 9 deletions(-)
>
> base-commit: 28955f4fa2823e39f1ecfb3a37a364563527afbc
next prev parent reply other threads:[~2024-11-14 11:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241114103151eucas1p133de0b231bf06bf8cd42621347a0ed17@eucas1p1.samsung.com>
2024-11-14 10:31 ` [PATCH 0/2] module: Block modules by Tuxedo from accessing GPL symbols Uwe Kleine-König
2024-11-14 10:31 ` [PATCH 1/2] module: Put known GPL offenders in an array Uwe Kleine-König
2024-11-14 16:08 ` Christoph Hellwig
2024-11-15 4:40 ` Greg KH
2024-11-14 10:31 ` [PATCH 2/2] module: Block modules by Tuxedo from accessing GPL symbols Uwe Kleine-König
2024-11-14 11:56 ` Daniel Gomez
2024-11-15 4:40 ` Greg KH
2024-11-14 16:09 ` Christoph Hellwig
2024-11-14 19:21 ` Aaron Rainbolt
2024-11-14 23:06 ` Al Viro
2024-11-15 4:40 ` Greg KH
2024-11-18 10:11 ` Werner Sembach
2024-11-14 10:49 ` [PATCH 0/2] " Werner Sembach
2024-11-14 11:14 ` Uwe Kleine-König
2024-11-14 11:44 ` Werner Sembach
2024-11-16 17:49 ` Uwe Kleine-König
2024-11-16 18:41 ` Werner Sembach
2024-11-15 4:43 ` Greg KH
2024-11-15 6:09 ` Werner Sembach
2024-11-15 6:30 ` Greg KH
2024-11-15 7:29 ` Uwe Kleine-König
2024-11-15 9:00 ` Werner Sembach
2024-11-15 9:18 ` Greg KH
2024-11-15 9:40 ` Werner Sembach
2024-11-15 10:22 ` Greg KH
2024-11-15 10:59 ` Werner Sembach
2024-11-15 12:01 ` Greg KH
2024-11-15 10:51 ` Uwe Kleine-König
2024-11-15 11:01 ` Werner Sembach
2024-11-14 11:50 ` Daniel Gomez [this message]
2024-11-20 14:11 ` Hans de Goede
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=D5LVNQFINITS.13C3C5UV89XRR@samsung.com \
--to=da.gomez@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=tux@tuxedocomputers.com \
--cc=ukleinek@kernel.org \
--cc=wse@tuxedocomputers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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