From: Catalin Marinas <catalin.marinas@arm.com>
To: Angelos Oikonomopoulos <angelos@igalia.com>
Cc: linux-arm-kernel@lists.infradead.org, will@kernel.org,
linux-kernel@vger.kernel.org, kernel-dev@igalia.com
Subject: Re: [PATCH] arm64: Don't call NULL in do_compat_alignment_fixup
Date: Fri, 28 Mar 2025 19:06:34 +0000 [thread overview]
Message-ID: <Z-bzOrF-4lSykkgJ@arm.com> (raw)
In-Reply-To: <20250326133521.13637-1-angelos@igalia.com>
On Wed, Mar 26, 2025 at 02:35:21PM +0100, Angelos Oikonomopoulos wrote:
> do_alignment_t32_to_handler only fixes up alignment faults for specific
> instructions; it returns NULL otherwise. When that's the case, signal to
> the caller that it needs to proceed with the regular alignment fault
> handling (i.e. SIGBUS).
Did you hit this in practice? Which instruction triggered the alignment
fault that was not handled by do_alignment_t32_to_handler()? Standard
LDR/STR should not trigger unaligned accesses unless you have some
device memory mapped in user space.
> Signed-off-by: Angelos Oikonomopoulos <angelos@igalia.com>
> ---
> arch/arm64/kernel/compat_alignment.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kernel/compat_alignment.c b/arch/arm64/kernel/compat_alignment.c
> index deff21bfa680..76cf1c1b5bc6 100644
> --- a/arch/arm64/kernel/compat_alignment.c
> +++ b/arch/arm64/kernel/compat_alignment.c
> @@ -34,7 +34,7 @@
>
> #define REGMASK_BITS(i) (i & 0xffff)
>
> -#define BAD_INSTR 0xdeadc0de
> +#define BAD_INSTR 0xdeadc0de
Unrelated change (white space I guess), please drop it, not worth
fixing.
--
Catalin
next prev parent reply other threads:[~2025-03-28 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 13:35 [PATCH] arm64: Don't call NULL in do_compat_alignment_fixup Angelos Oikonomopoulos
2025-03-28 19:06 ` Catalin Marinas [this message]
2025-03-31 7:57 ` Angelos Oikonomopoulos
-- strict thread matches above, loose matches on Subject: below --
2025-03-31 8:54 Angelos Oikonomopoulos
2025-04-01 6:05 ` Anshuman Khandual
2025-04-01 6:58 ` Angelos Oikonomopoulos
2025-04-01 7:47 ` Anshuman Khandual
2025-04-01 8:09 ` Angelos Oikonomopoulos
2025-04-01 8:22 ` Anshuman Khandual
2025-04-01 8:58 ` Angelos Oikonomopoulos
2025-04-04 13:58 ` 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=Z-bzOrF-4lSykkgJ@arm.com \
--to=catalin.marinas@arm.com \
--cc=angelos@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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