From: Heiko Carstens <hca@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
imbrenda@linux.ibm.com, borntraeger@linux.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/mm: add missing secure storage access fixups for donated memory
Date: Mon, 9 Mar 2026 14:31:35 +0100 [thread overview]
Message-ID: <20260309133135.30265H8b-hca@linux.ibm.com> (raw)
In-Reply-To: <20260309125311.31937-5-frankja@linux.ibm.com>
On Mon, Mar 09, 2026 at 12:53:15PM +0000, Janosch Frank wrote:
> There are special cases where secure storage access exceptions happen
> in a kernel context for pages that don't have the PG_arch_1 bit
> set. That bit is set for non-exported guest secure storage (memory)
> but is absent on storage donated to the Ultravisor since the kernel
> isn't allowed to export donated pages.
>
> Prior to this patch we would try to export the page by calling
> arch_make_folio_accessible() which would instantly return since the
> arch bit is absent signifying that the page was already exported and
> no further action is necessary. This leads to secure storage access
> exception loops which can never be resolved.
>
> With this patch we unconditionally try to export and if that fails we
> fixup.
>
> Fixes: 084ea4d611a3 ("s390/mm: add (non)secure page access exceptions handlers")
> Reported-by: Heiko Carstens <hca@linux.ibm.com>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> ---
> arch/s390/mm/fault.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/arch/s390/mm/fault.c b/arch/s390/mm/fault.c
> index a52aa7a99b6b..71bad4257aab 100644
> --- a/arch/s390/mm/fault.c
> +++ b/arch/s390/mm/fault.c
> @@ -441,10 +441,15 @@ void do_secure_storage_access(struct pt_regs *regs)
> folio = phys_to_folio(addr);
> if (unlikely(!folio_try_get(folio)))
> return;
> - rc = arch_make_folio_accessible(folio);
> + rc = uv_convert_from_secure(folio_to_phys(folio));
> folio_put(folio);
> + /*
> + * There are some valid fixup types for kernel
> + * accesses to donated secure memory. zeropad is one
> + * of them.
> + */
> if (rc)
> - BUG();
> + return handle_fault_error(regs, 0);
This context doesn't hold mmlock, so it should be:
return handle_fault_error_nolock(regs, 0);
And, yes, you can blame me, since I proposed the wrong call off-list.
prev parent reply other threads:[~2026-03-09 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 12:53 [PATCH] s390/mm: add missing secure storage access fixups for donated memory Janosch Frank
2026-03-09 13:31 ` Heiko Carstens [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=20260309133135.30265H8b-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@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