From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Arnd Bergmann <arnd@kernel.org>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
"T.J. Mercier" <tjmercier@google.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Maxime Ripard <mripard@kernel.org>, Andrew Davis <afd@ti.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Sven Schnelle <svens@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
"David Hildenbrand (Arm)" <david@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] s390: export memory encryption helper functions
Date: Tue, 9 Jun 2026 14:38:45 +0200 [thread overview]
Message-ID: <7bb6c04b-ded9-47e3-9350-563344de9f80@linux.ibm.com> (raw)
In-Reply-To: <20260526102113.2594501-1-arnd@kernel.org>
Am 26.05.26 um 12:20 schrieb Arnd Bergmann:
> From: Arnd Bergmann <arnd@arndb.de>
>
> The set_memory_encrypted/set_memory_decrypted functions are exported
> on x86 and arm64 but not on s390, which leads to a new build failure
> because they are now used in a loadable module:
>
> ERROR: modpost: "set_memory_encrypted" [drivers/dma-buf/heaps/system_heap.ko] undefined!
> ERROR: modpost: "set_memory_decrypted" [drivers/dma-buf/heaps/system_heap.ko] undefined!
>
> Export these the same way we do on the other architectures.
>
> Fixes: fd55edff8a0a ("dma-buf: heaps: system: Turn the heap into a module")
This commit id was from an next tree? Seems to be no longer valid.
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Christian Borntraeger <borntraeger@linux.ibm.com>
@Alexander/vasily/Heiko, can you maybe queue that via the s390 fixes tree?> ---
> 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 f07168a0d3dd..d589c5e4d388 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)
next prev parent reply other threads:[~2026-06-09 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 10:20 Arnd Bergmann
2026-05-26 10:20 ` [PATCH 2/2] powerpc: " Arnd Bergmann
2026-05-26 11:53 ` Christophe Leroy (CS GROUP)
2026-05-26 10:59 ` [PATCH 1/2] s390: " Claudio Imbrenda
2026-06-09 12:20 ` Uwe Kleine-König
2026-06-09 12:38 ` Christian Borntraeger [this message]
2026-06-09 13:33 ` 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=7bb6c04b-ded9-47e3-9350-563344de9f80@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=afd@ti.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=david@kernel.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=rppt@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=svens@linux.ibm.com \
--cc=tjmercier@google.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
Powered by JetHome