From: "T.J. Mercier" <tjmercier@google.com>
To: agordeev@linux.ibm.com, gerald.schaefer@linux.ibm.com,
linux-s390@vger.kernel.org, mripard@kernel.org,
sumit.semwal@linaro.org
Cc: linux-kernel@vger.kernel.org, "T.J. Mercier" <tjmercier@google.com>
Subject: [PATCH] s390/mm: Export set_memory_encrypted and set_memory_decrypted
Date: Fri, 22 May 2026 16:06:05 -0700 [thread overview]
Message-ID: <20260522230606.883180-1-tjmercier@google.com> (raw)
After commit fd55edff8a0a ("dma-buf: heaps: system: Turn the heap into a
module") the system dma-buf heaps can be built as a module. The
system_cc_shared heap uses set_memory_encrypted and set_memory_decrypted
but those functions are not exported on s390. This results in a build
error like:
>> ERROR: modpost: "set_memory_decrypted" [drivers/dma-buf/heaps/system_heap.ko] undefined!
>> ERROR: modpost: "set_memory_encrypted" [drivers/dma-buf/heaps/system_heap.ko] undefined!
Export the functions so system_heap.ko can be built.
Fixes: fd55edff8a0a ("dma-buf: heaps: system: Turn the heap into a module")
Signed-off-by: T.J. Mercier <tjmercier@google.com>
---
arch/s390/mm/init.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/s390/mm/init.c b/arch/s390/mm/init.c
index 36bd9530db52..8244b57da31c 100644
--- a/arch/s390/mm/init.c
+++ b/arch/s390/mm/init.c
@@ -124,6 +124,7 @@ int set_memory_encrypted(unsigned long vaddr, int numpages)
}
return 0;
}
+EXPORT_SYMBOL_GPL(set_memory_encrypted);
int set_memory_decrypted(unsigned long vaddr, int numpages)
{
@@ -135,6 +136,7 @@ int set_memory_decrypted(unsigned long vaddr, int numpages)
}
return 0;
}
+EXPORT_SYMBOL_GPL(set_memory_decrypted);
/* are we a protected virtualization guest? */
bool force_dma_unencrypted(struct device *dev)
--
2.54.0.746.g67dd491aae-goog
next reply other threads:[~2026-05-22 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 23:06 T.J. Mercier [this message]
2026-05-23 16:01 ` Heiko Carstens
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=20260522230606.883180-1-tjmercier@google.com \
--to=tjmercier@google.com \
--cc=agordeev@linux.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=sumit.semwal@linaro.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®