From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Orzel, Michal" <michal.orzel@amd.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Oleksii Kurochko <oleksii.kurochko@gmail.com>
Subject: Re: [PATCH for-4.20? 1/4] ARM32/traps: Fix do_trap_undefined_instruction()'s detection of kernel text
Date: Mon, 10 Feb 2025 22:31:36 +0000 [thread overview]
Message-ID: <37634e0f-3bc2-46d7-96df-f9bf4be3e6cb@citrix.com> (raw)
In-Reply-To: <b829abd1-e0b0-4f36-bc27-0f632deedbab@amd.com>
On 10/02/2025 10:13 am, Orzel, Michal wrote:
>
> On 08/02/2025 01:02, Andrew Cooper wrote:
>>
>> While fixing some common/arch boundaries for UBSAN support on other
>> architectures, the following debugging patch:
>>
>> diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
>> index c1f2d1b89d43..58d1d048d339 100644
>> --- a/xen/arch/arm/setup.c
>> +++ b/xen/arch/arm/setup.c
>> @@ -504,6 +504,8 @@ void asmlinkage __init start_xen(unsigned long fdt_paddr)
>>
>> system_state = SYS_STATE_active;
>>
>> + dump_execution_state();
>> +
>> for_each_domain( d )
>> domain_unpause_by_systemcontroller(d);
>>
>> fails with:
>>
>> (XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
>> (XEN) CPU0: Unexpected Trap: Undefined Instruction
>> (XEN) ----[ Xen-4.20-rc arm32 debug=n Not tainted ]----
>> (XEN) CPU: 0
>> <snip>
>> (XEN)
>> (XEN) ****************************************
>> (XEN) Panic on CPU 0:
>> (XEN) CPU0: Unexpected Trap: Undefined Instruction
>> (XEN) ****************************************
>>
>> This is because the condition for init text is wrong. While there's nothing
>> interesting from that point onwards in start_xen(), it's also wrong for any
>> livepatch which brings in an adjusted BUG_FRAME().
>>
>> Use is_active_kernel_text() which is the correct test for this purpose, and is
>> aware of init and livepatch regions too.
>>
>> Commit c8d4b6304a5e ("xen/arm: add support for run_in_exception_handler()"),
>> made run_in_exception_handler() work, but didn't complete the TODO left in
>> commit 3e802c6ca1fb ("xen/arm: Correctly support WARN_ON"). Do so, to make
>> ARM consistent with other architectures.
>>
>> Fixes: 3e802c6ca1fb ("xen/arm: Correctly support WARN_ON")
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> You should have mentioned that this patch requires [1] as a prerequisite.
> Otherwise this patch fails to build on both arm64 and arm32 with UBSAN enabled.
>
> [1]
> https://lore.kernel.org/xen-devel/359347d3-9a5f-4672-98d6-4c497d960059@gmail.com/T/#mc75e1b1ff6ccf4b0c7e10f55eedb7cacffca1c3d
That is unintentional.
I'm going to split this patch in half, because it's clear that the
run_in_exception_handler() problems are more complicated than I expected.
The fix in do_trap_undefined_instruction() genuinely is entirely
independent of UBSAN.
~Andrew
next prev parent reply other threads:[~2025-02-10 22:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 0:02 [PATCH 0/4] Other fixes from UBSAN enablement Andrew Cooper
2025-02-08 0:02 ` [PATCH for-4.20? 1/4] ARM32/traps: Fix do_trap_undefined_instruction()'s detection of kernel text Andrew Cooper
2025-02-10 10:13 ` Orzel, Michal
2025-02-10 22:31 ` Andrew Cooper [this message]
2025-02-10 21:23 ` Julien Grall
2025-02-10 22:23 ` Andrew Cooper
2025-02-11 10:05 ` Julien Grall
2025-02-08 0:02 ` [PATCH 2/4] ARM: Fix register constraints in run_in_exception_handler() Andrew Cooper
2025-02-10 9:21 ` Oleksii Kurochko
2025-02-10 21:31 ` Julien Grall
2025-02-10 22:41 ` Andrew Cooper
2025-02-12 22:59 ` Julien Grall
2025-02-10 10:33 ` Orzel, Michal
2025-02-10 21:29 ` Julien Grall
2025-02-10 22:10 ` Andrew Cooper
2025-02-08 0:02 ` [PATCH 3/4] xen: Centralise the declaration of dump_execution_state() Andrew Cooper
2025-02-10 9:23 ` Oleksii Kurochko
2025-02-10 9:25 ` Jan Beulich
2025-02-08 0:02 ` [PATCH 4/4] [BROKEN] PPC: Activate UBSAN in testing Andrew Cooper
2025-02-21 19:49 ` Shawn Anastasio
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=37634e0f-3bc2-46d7-96df-f9bf4be3e6cb@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.