From: Mark Rutland <mark.rutland@arm.com>
To: "Brandt, Oliver - Lenze" <oliver.brandt@lenze.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"will@kernel.org" <will@kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: mm: disable PAN during caches_clean_inval_user_pou
Date: Mon, 8 Jan 2024 15:54:58 +0000 [thread overview]
Message-ID: <ZZwa0msD9KSJg54-@FVFF77S0Q05N> (raw)
In-Reply-To: <e6dc8a44a140d1e54bc1408c36704b581433ec10.camel@lenze.com>
Hi Oliver,
On Mon, Jan 08, 2024 at 01:00:39PM +0000, Brandt, Oliver - Lenze wrote:
> Using the cacheflush() syscall from an 32-bit user-space fails when
> ARM64_PAN is used. We 'll get an endless loop:
>
> 1. executing "dc cvau, x2" results in raising an abort
> 2. abort handler does not fix the reason for the abort and
> returns to 1.
>
> Disabling PAN for the time of the cache maintenance fixes this.
Hmm... the ARM ARM says PSTATE.PAN is not supposed to affect DC CVAU.
Looking at the latest ARM ARM (ARM DDI 0487J.a), R_PMTWB states:
| The PSTATE.PAN bit has no effect on all of the following:
|
| o Instruction fetches.
| o Data cache instructions, except DC ZVA.
| o If FEAT_PAN2 is not implemented, then address translation instructions.
| o If FEAT_PAN2 is implemented, then the address translation instructions
| other than AT S1E1RP and AT S1E1WP.
So IIUC, DC CVAU shouldn't be affected by PAN.
This could be a CPU bug; which CPU are you seeing this with?
Mark.
> Fixes: 338d4f49d6f7 ("arm64: kernel: Add support for Privileged Access Never")
> Cc: stable@vger.kernel.org
> Signed-off-by: Oliver Brandt <oliver.brandt@lenze.com>
> ---
> arch/arm64/mm/cache.S | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/mm/cache.S b/arch/arm64/mm/cache.S
> index 503567c864fde..333c4c2baa568 100644
> --- a/arch/arm64/mm/cache.S
> +++ b/arch/arm64/mm/cache.S
> @@ -70,10 +70,12 @@ SYM_FUNC_ALIAS(__pi_caches_clean_inval_pou, caches_clean_inval_pou)
> */
> SYM_FUNC_START(caches_clean_inval_user_pou)
> uaccess_ttbr0_enable x2, x3, x4
> + ALTERNATIVE("nop", SET_PSTATE_PAN(0), ARM64_HAS_PAN, CONFIG_ARM64_PAN)
>
> caches_clean_inval_pou_macro 2f
> mov x0, xzr
> 1:
> + ALTERNATIVE("nop", SET_PSTATE_PAN(1), ARM64_HAS_PAN, CONFIG_ARM64_PAN)
> uaccess_ttbr0_disable x1, x2
> ret
> 2:
> --
> 2.43.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-08 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 13:00 [PATCH] arm64: mm: disable PAN during caches_clean_inval_user_pou Brandt, Oliver - Lenze
2024-01-08 15:54 ` Mark Rutland [this message]
2024-01-08 16:37 ` Brandt, Oliver - Lenze
2024-01-08 17:58 ` Mark Rutland
2024-01-09 8:37 ` Brandt, Oliver - Lenze
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=ZZwa0msD9KSJg54-@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.brandt@lenze.com \
--cc=will@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