From: Christoph Hellwig <hch@lst.de>
To: Jessica Yu <jeyu@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org (open list)
Subject: inherit TAINT_PROPRIETARY_MODULE
Date: Wed, 29 Jul 2020 08:27:04 +0200 [thread overview]
Message-ID: <20200729062711.13016-1-hch@lst.de> (raw)
Hi Jessica,
we've had a bug in our resolution of _GPL modules since day one, that
is a module can claim to be GPL licensed and use _GPL exports, while
it also depends on symbols from non-GPL modules. This is used as a
circumvention of the _GPL exports by using a small shim module using
the _GPL exports and the other functionality. A recent example can
be found here:
https://lore.kernel.org/netdev/6376CA34-BC6F-45DE-9FFD-7E32664C7569@fb.com/T/#md514322fdfa212afe9f1d3eb4e5f7eaefece36eb
Diffstat:
include/linux/module.h | 24 ++----------------------
kernel/module.c | 42 +++++++++++++++++++++++++++---------------
2 files changed, 29 insertions(+), 37 deletions(-)
next reply other threads:[~2020-07-29 6:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 6:27 Christoph Hellwig [this message]
2020-07-29 6:27 ` [PATCH 1/7] modules: mark ref_module static Christoph Hellwig
2020-07-29 6:27 ` [PATCH 2/7] modules: mark find_symbol static Christoph Hellwig
2020-07-29 16:13 ` Jessica Yu
2020-07-29 16:24 ` Greg Kroah-Hartman
2020-07-29 17:06 ` Christoph Hellwig
2020-07-29 17:25 ` Joe Lawrence
2020-07-29 6:27 ` [PATCH 3/7] modules: mark each_symbol_section static Christoph Hellwig
2020-07-29 6:27 ` [PATCH 4/7] modules: unexport __module_text_address Christoph Hellwig
2020-07-29 6:27 ` [PATCH 5/7] modules: unexport __module_address Christoph Hellwig
2020-07-29 6:27 ` [PATCH 6/7] modules: return licensing information from find_symbol Christoph Hellwig
2020-07-29 16:48 ` Jessica Yu
2020-07-29 17:06 ` Christoph Hellwig
2020-07-29 6:27 ` [PATCH 7/7] modules: inherit TAINT_PROPRIETARY_MODULE Christoph Hellwig
2020-07-29 6:55 ` Greg Kroah-Hartman
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=20200729062711.13016-1-hch@lst.de \
--to=hch@lst.de \
--cc=gregkh@linuxfoundation.org \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®