From: Catalin Marinas <catalin.marinas@arm.com>
To: Shiqi Liu <shiqiliu@hust.edu.cn>
Cc: will@kernel.org, broonie@kernel.org, anshuman.khandual@arm.com,
maz@kernel.org, suzuki.poulose@arm.com, miguel.luis@oracle.com,
joey.gouly@arm.com, oliver.upton@linux.dev,
jingzhangos@google.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/sysreg: Update PIE permission encodings
Date: Mon, 22 Apr 2024 11:09:34 +0100 [thread overview]
Message-ID: <ZiY3Xhcg5hH5ZTB4@arm.com> (raw)
In-Reply-To: <20240421063328.29710-1-shiqiliu@hust.edu.cn>
On Sun, Apr 21, 2024 at 02:33:28PM +0800, Shiqi Liu wrote:
> Fix left shift overflow issue when the parameter idx is greater than or
> equal to 8 in the calculation of perm in PIRx_ELx_PERM macro.
>
> Fix this by modifying the encoding to use a long integer type.
>
> Signed-off-by: Shiqi Liu <shiqiliu@hust.edu.cn>
> ---
> arch/arm64/include/asm/sysreg.h | 24 ++++++++++++------------
> tools/arch/arm64/include/asm/sysreg.h | 24 ++++++++++++------------
> 2 files changed, 24 insertions(+), 24 deletions(-)
>
> diff --git a/arch/arm64/include/asm/sysreg.h b/arch/arm64/include/asm/sysreg.h
> index 9e8999592f3a..af3b206fa423 100644
> --- a/arch/arm64/include/asm/sysreg.h
> +++ b/arch/arm64/include/asm/sysreg.h
> @@ -1036,18 +1036,18 @@
> * Permission Indirection Extension (PIE) permission encodings.
> * Encodings with the _O suffix, have overlays applied (Permission Overlay Extension).
> */
> -#define PIE_NONE_O 0x0
> -#define PIE_R_O 0x1
> -#define PIE_X_O 0x2
> -#define PIE_RX_O 0x3
> -#define PIE_RW_O 0x5
> -#define PIE_RWnX_O 0x6
> -#define PIE_RWX_O 0x7
> -#define PIE_R 0x8
> -#define PIE_GCS 0x9
> -#define PIE_RX 0xa
> -#define PIE_RW 0xc
> -#define PIE_RWX 0xe
> +#define PIE_NONE_O UL(0x0)
> +#define PIE_R_O UL(0x1)
> +#define PIE_X_O UL(0x2)
> +#define PIE_RX_O UL(0x3)
> +#define PIE_RW_O UL(0x5)
> +#define PIE_RWnX_O UL(0x6)
> +#define PIE_RWX_O UL(0x7)
> +#define PIE_R UL(0x8)
> +#define PIE_GCS UL(0x9)
> +#define PIE_RX UL(0xa)
> +#define PIE_RW UL(0xc)
> +#define PIE_RWX UL(0xe)
>
> #define PIRx_ELx_PERM(idx, perm) ((perm) << ((idx) * 4))
Thanks. That's indeed the better way to write these constants, they also
match the POE_* macros further down in this file.
Currently nothing is broken since the PIE_E0 and PIE_E1 macros are only
used in assembly where the UL() doesn't have any effect but we may
change it in the future. I'll leave it with Will to pick up.
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
_______________________________________________
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-04-22 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 6:33 [PATCH] arm64/sysreg: Update PIE permission encodings Shiqi Liu
2024-04-21 9:40 ` Marc Zyngier
2024-04-22 10:09 ` Catalin Marinas [this message]
2024-04-28 8:59 ` Will Deacon
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=ZiY3Xhcg5hH5ZTB4@arm.com \
--to=catalin.marinas@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=jingzhangos@google.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=miguel.luis@oracle.com \
--cc=oliver.upton@linux.dev \
--cc=shiqiliu@hust.edu.cn \
--cc=suzuki.poulose@arm.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;
as well as URLs for NNTP newsgroup(s).