From: "Angelos Oikonomopoulos" <angelos@igalia.com>
To: "Catalin Marinas" <catalin.marinas@arm.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: Mon, 31 Mar 2025 09:57:17 +0200 [thread overview]
Message-ID: <D8UAHZY0DJ19.18319MPVM5SPC@igalia.com> (raw)
In-Reply-To: <Z-bzOrF-4lSykkgJ@arm.com>
On Fri Mar 28, 2025 at 8:06 PM CET, Catalin Marinas wrote:
> 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.
Yah, I've hit this in practice. The offending instruction was an ldrex
to an unaligned address, while running 32-bit code on an "Ampere(R)
Altra(R) Processor Q80-30 CPU @ 3.0GHz". Fixing the unaligned access in
the program is one thing, but this resulted in multiple oopses in CI.
>> #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.
That snuck past me in an amend, will send a v2.
Thanks,
Angelos
next prev parent reply other threads:[~2025-03-31 7:57 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
2025-03-31 7:57 ` Angelos Oikonomopoulos [this message]
-- 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=D8UAHZY0DJ19.18319MPVM5SPC@igalia.com \
--to=angelos@igalia.com \
--cc=catalin.marinas@arm.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