public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sebastian Gottschall <s.gottschall@newmedia-net.de>
Cc: "Ingo Molnar" <mingo@kernel.org>,
	"Jiri Kosina" <jikos@kernel.org>,
	"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
	"Andy Lutomirski" <luto@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Rik van Riel" <riel@surriel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Nicolai Stange" <nstange@suse.de>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	x86@kernel.org, stable@vger.kernel.org,
	"Jiri Kosina" <jikos@jikos.cz>
Subject: Re: [PATCH] x86/fpu: Remove the _GPL from the kernel_fpu_begin/end() export
Date: Sat, 4 May 2019 08:40:41 +0200	[thread overview]
Message-ID: <20190504064041.GB26311@kroah.com> (raw)
In-Reply-To: <2238f6ed-9338-903c-760c-6200e73b1599@newmedia-net.de>

On Sat, May 04, 2019 at 04:28:17AM +0200, Sebastian Gottschall wrote:
> 
> Am 04.05.2019 um 02:47 schrieb Ingo Molnar:
> > * Jiri Kosina <jikos@kernel.org> wrote:
> > 
> > > On Thu, 2 May 2019, Sebastian Andrzej Siewior wrote:
> > > 
> > > > Please don't start this. We have everything _GPL that is used for FPU
> > > > related code and only a few functions are exported because KVM needs it.
> > > That's not completely true. There are a lot of static inlines out there,
> > > which basically made it possible for external modules to use FPU (in some
> > > way) when they had kernel_fpu_[begin|end]() available.
> > > 
> > > I personally don't care about ZFS a tiny little bit; but in general, the
> > > current situation with _GPL and non-_GPL exports is simply not nice. It's
> > > not really about licensing (despite the name), it's about 'internal vs
> > > external', which noone is probably able to define properly.
> > But that's exactly what licensing *IS* about: the argument is that
> > 'internal' interfaces are clear proof that the binary module is actually
> > a derived work of the kernel.
> Using fpu code in kernel space in a kernel module is a derived work of the
> kernel itself?
> dont get me wrong, but this is absurd. i mean you limit the use of cpu
> instructions. the use
> of cpu instructions should be free of any licensing issue. i would even
> argument you are violating
> the license of the cpu ower given to the kernel by executing it, by
> restricting its use for no reason

Now you are just being crazy, please go talk to a lawyer about how the
GPL actually works.

If Andy wants to change the symbol of what he wrote from
EXPORT_SYMBOL_GPL() to EXPORT_SYMBOL(), that's fine, it's his option.
Any loony discussion about if this is actually a licensing issue or not
needs to just go to /dev/null

As homework, everyone please go read this:
	http://softwarefreedom.org/resources/2014/SFLC-Guide_to_GPL_Compliance_2d_ed.pdf
and remember that the license of the Linux kernel is GPLv2.

Now where's the "kill this thread" option on mutt so I don't have to see
any more of this nonsense...

greg k-h

  reply	other threads:[~2019-05-04  6:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02 14:42 [PATCH] x86/fpu: Remove the _GPL from the kernel_fpu_begin/end() export Andy Lutomirski
2019-05-02 15:40 ` Sebastian Andrzej Siewior
2019-05-02 16:29   ` Andy Lutomirski
2019-05-02 16:55     ` Borislav Petkov
2019-05-03 17:21       ` Paolo Bonzini
2019-05-03 18:07         ` Borislav Petkov
2019-05-03 18:54           ` Andy Lutomirski
2019-05-03 19:07             ` Borislav Petkov
2019-05-03 18:49   ` Jiri Kosina
2019-05-04  0:47     ` Ingo Molnar
2019-05-04  2:28       ` Sebastian Gottschall
2019-05-04  6:40         ` Greg KH [this message]
2019-05-05 16:05         ` Rik van Riel
2019-05-05 19:09           ` Jiri Kosina
2019-05-04  7:26     ` Jiri Kosina
2019-05-07 10:31       ` David Laight
2019-05-08 12:28         ` Sebastian Gottschall
2019-05-08 12:51           ` Greg KH

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=20190504064041.GB26311@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Jason@zx2c4.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bigeasy@linutronix.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jikos@jikos.cz \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=nstange@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=riel@surriel.com \
    --cc=rkrcmar@redhat.com \
    --cc=s.gottschall@newmedia-net.de \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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