From: Will Deacon <will@kernel.org>
To: Pepper Gray <hello@peppergray.xyz>
Cc: linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
ardb@kernel.org
Subject: Re: [PATCH] arm64/scs: Fix handling of advance_loc4
Date: Thu, 12 Mar 2026 13:59:30 +0000 [thread overview]
Message-ID: <abLGwg1aFyoCosHi@willie-the-truck> (raw)
In-Reply-To: <CAC+fAGbCjQSGbtkbGr5Qb=tPez1i4KZ7TtC0DPHxGbC0wLvBAw@mail.gmail.com>
[+Ard]
On Tue, Mar 10, 2026 at 03:15:56PM +0100, Pepper Gray wrote:
> DW_CFA_advance_loc4 is defined but no handler is implemented. Its
> CFA opcode defaults to EDYNSCS_INVALID_CFA_OPCODE triggering an
> error which wrongfully prevents modules from loading.
Can you provide some instructions for reproducing this, please? For
example, which toolchain you are using and which module are you building?
> Signed-off-by: Pepper Gray <hello@peppergray.xyz>
> ---
> arch/arm64/kernel/pi/patch-scs.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm64/kernel/pi/patch-scs.c b/arch/arm64/kernel/pi/patch-scs.c
> index bbe7d30ed12b32..dac568e4a54f23 100644
> --- a/arch/arm64/kernel/pi/patch-scs.c
> +++ b/arch/arm64/kernel/pi/patch-scs.c
> @@ -192,6 +192,14 @@ static int scs_handle_fde_frame(const struct
> eh_frame *frame,
> size -= 2;
> break;
>
> + case DW_CFA_advance_loc4:
> + loc += *opcode++ * code_alignment_factor;
> + loc += (*opcode++ << 8) * code_alignment_factor;
> + loc += (*opcode++ << 16) * code_alignment_factor;
> + loc += (*opcode++ << 24) * code_alignment_factor;
> + size -= 4;
> + break;
This looks like it's whitespace-mangled to me.
Will
next prev parent reply other threads:[~2026-03-12 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 14:15 [PATCH] arm64/scs: Fix handling of advance_loc4 Pepper Gray
2026-03-12 13:59 ` Will Deacon [this message]
2026-03-12 15:06 ` Ard Biesheuvel
[not found] ` <CAHLDejw4XKZ3-dbFFRYVGAZyYkmkzW5cdkvJNVJ9p3ARMUUyjQ@mail.gmail.com>
2026-03-13 16:57 ` Will Deacon
[not found] ` <CAHLDejz=-kHt4xXmf3K4A+jj5aj+JD3LJta7SGEOK6G4SxxGdQ@mail.gmail.com>
2026-03-17 15:00 ` Ard Biesheuvel
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=abLGwg1aFyoCosHi@willie-the-truck \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=hello@peppergray.xyz \
--cc=linux-arm-kernel@lists.infradead.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