[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFz5Z8dfLp1swfOaEomH21mvCFEy=4w6L0cWska=He45FQ@mail.gmail.com>
Date: Wed, 8 Nov 2017 13:09:29 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Jiri Kosina <jikos@...nel.org>, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Tom Lendacky <thomas.lendacky@....com>,
Borislav Petkov <bp@...e.de>,
LKML <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
Greg KH <greg@...ah.com>
Subject: Re: [PATCH] x86/mm: Unbreak modules that rely on external PAGE_KERNEL availability
On Wed, Nov 8, 2017 at 12:47 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
>
> Despised-by: Thomas Gleixner <tglx@...utronix.de>
So I despise the patch for a different reason: I hate it when we
export data symbols like this.
But that's independent of the GPL-vs-not issue, and it's not like this
is the first time it happens.
Generally we should export _functionality_, not data.
The fact that we need to export access to some random global data that
we then use in an inline function or macro to me says that the code
was not designed right to begin with.
But yeah, I guess we can't fix that easily as-is, and people who just
randomly slap _GPL() on the export should stop doing that. It's *not*
a default thing, quite the reverse. It should be something that is so
core - but also so _meaningful_ - that using it is a big flag that
you're not just a random driver or something.
So slapping _GPL on some random piece of data that that doesn't
actually imply anything at all for copyright derivation is
fundamentally broken and stupid.
Linus
Powered by blists - more mailing lists