From: Tj <linux@iam.tj>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: linux-mm@kvack.org, linux-arch@vger.kernel.org
Subject: Regression: x86/mm: Add Secure Memory Encryption (SME) support
Date: Sat, 30 Sep 2017 23:36:35 +0100 [thread overview]
Message-ID: <d5c60048-dbb3-0440-d139-ea325621e654@iam.tj> (raw)
With 4.14.0rc2 on an Intel CPU with an Nvidia GPU the proprietary nvidia
driver (v340.102) fails to modpost due to:
FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'sme_me_mask'
I think this is due to:
config ARCH_HAS_MEM_ENCRYPT
def_bool y
I noticed that a grep of the built kernel for "sme_me_mask" shows the
symbol imported into more than 300 modules on an Ubuntu mainline build
of 4.14.0-041400rc2-lowlatency.
Should the new symbol be referenced so widely and how can it be
prevented from being included in proprietary modules on systems that
don't have SME even if the kernel is built with it enabled?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-09-30 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 22:36 Tj [this message]
2017-10-02 16:30 ` Tom Lendacky
2017-10-19 19:36 ` Thomas Gleixner
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=d5c60048-dbb3-0440-d139-ea325621e654@iam.tj \
--to=linux@iam.tj \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=thomas.lendacky@amd.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