From: Christoph Hellwig <hch@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
Christoph Hellwig <hch@infradead.org>,
"T.J. Mercier" <tjmercier@google.com>,
maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
chleroy@kernel.org, linuxppc-dev@lists.ozlabs.org,
mripard@kernel.org, sumit.semwal@linaro.org, lkp@intel.com,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
linux-mm@kvack.org, agordeev@linux.ibm.com,
gerald.schaefer@linux.ibm.com, linux-s390@vger.kernel.org,
Dan Williams <djbw@kernel.org>,
Tom Lendacky <thomas.lendacky@amd.com>,
x86@kernel.org
Subject: Re: [PATCH] powerpc: Export set_memory_encrypted and set_memory_decrypted
Date: Thu, 28 May 2026 01:53:17 -0700 [thread overview]
Message-ID: <ahgCfazNTdk7Em-K@infradead.org> (raw)
In-Reply-To: <20260527181549.GBahc01Xflm2yo5OqI@fat_crate.local>
On Wed, May 27, 2026 at 11:15:49AM -0700, Borislav Petkov wrote:
> On Wed, May 27, 2026 at 01:07:16PM -0300, Jason Gunthorpe wrote:
> > > Setting memory decrypted is a dangerous operations and should only
> > > be available to core code. We should have various allocators for
> > > decrypted code, but not export the functionality to random code.
> >
> > At the very least an EXPORT_SYMBOL_NS.
> >
> > Looks like there are about 3 modules using it already..
>
> Looks like more to me...
>
> In any case, we exported them back then for some framebuffer things:
>
> 95cf9264d5f3 ("x86, drm, fbdev: Do not specify encrypted memory for video mappings")
Which is exactly one of these things that should not happen - mapping
random I/O memory without the proper helpers..
prev parent reply other threads:[~2026-05-28 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260522225853.878411-1-tjmercier@google.com>
2026-05-25 6:21 ` [PATCH] powerpc: Export set_memory_encrypted and set_memory_decrypted Christoph Hellwig
2026-05-27 16:07 ` Jason Gunthorpe
2026-05-27 18:15 ` Borislav Petkov
2026-05-28 8:53 ` Christoph Hellwig [this message]
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=ahgCfazNTdk7Em-K@infradead.org \
--to=hch@infradead.org \
--cc=agordeev@linux.ibm.com \
--cc=bp@alien8.de \
--cc=chleroy@kernel.org \
--cc=djbw@kernel.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=mripard@kernel.org \
--cc=npiggin@gmail.com \
--cc=sumit.semwal@linaro.org \
--cc=thomas.lendacky@amd.com \
--cc=tjmercier@google.com \
--cc=x86@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