From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] arm64/signal: Silence spurious sparse warning storing GCSPR_EL0
Date: Tue, 10 Dec 2024 14:17:58 +0000 [thread overview]
Message-ID: <Z1hNllCWa4u-IxrH@arm.com> (raw)
In-Reply-To: <20241210-arm64-gcs-signal-sparse-v1-1-26888bcd6f89@kernel.org>
On Tue, Dec 10, 2024 at 12:42:53AM +0000, Mark Brown wrote:
> diff --git a/arch/arm64/kernel/signal.c b/arch/arm64/kernel/signal.c
> index 14ac6fdb872b9672e4b16a097f1b577aae8dec50..83ea7e5fd2b54566c6649b82b8570657a5711dd4 100644
> --- a/arch/arm64/kernel/signal.c
> +++ b/arch/arm64/kernel/signal.c
> @@ -39,7 +39,7 @@
> #ifdef CONFIG_ARM64_GCS
> #define GCS_SIGNAL_CAP(addr) (((unsigned long)addr) & GCS_CAP_ADDR_MASK)
>
> -static bool gcs_signal_cap_valid(u64 addr, u64 val)
> +static bool gcs_signal_cap_valid(unsigned long __user *addr, u64 val)
> {
> return val == GCS_SIGNAL_CAP(addr);
> }
> @@ -1094,15 +1094,15 @@ static int gcs_restore_signal(void)
> /*
> * Check that the cap is the actual GCS before replacing it.
> */
> - if (!gcs_signal_cap_valid((u64)gcspr_el0, cap))
> + if (!gcs_signal_cap_valid(gcspr_el0, cap))
> return -EINVAL;
>
> /* Invalidate the token to prevent reuse */
> - put_user_gcs(0, (__user void*)gcspr_el0, &ret);
> + put_user_gcs(0, gcspr_el0, &ret);
> if (ret != 0)
> return -EFAULT;
>
> - write_sysreg_s(gcspr_el0 + 1, SYS_GCSPR_EL0);
> + write_sysreg_s((unsigned long)(gcspr_el0 + 1), SYS_GCSPR_EL0);
Would we now get a warning here?
--
Catalin
next prev parent reply other threads:[~2024-12-10 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 0:42 [PATCH] arm64/signal: Silence spurious sparse warning storing GCSPR_EL0 Mark Brown
2024-12-10 14:17 ` Catalin Marinas [this message]
2024-12-10 14:45 ` Mark Brown
2024-12-10 14:48 ` Mark Rutland
2024-12-10 15:44 ` Mark Brown
2024-12-10 16:35 ` Mark Rutland
2024-12-10 16:52 ` Mark Brown
2024-12-13 16:17 ` Catalin Marinas
2024-12-13 17:21 ` Mark Brown
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=Z1hNllCWa4u-IxrH@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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).