From: Andrew Cooper Date: Wed, 15 Jan 2020 18:43:58 +0000 (+0000) Subject: ARM/boot: Don't poison 'current' during early boot X-Git-Tag: archive/raspbian/4.14.0+80-gd101b417b7-1+rpi1^2~63^2~888 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=1a42c2fcd29642ceaae9e5a12bb9c5c6f4b92813;p=xen.git ARM/boot: Don't poison 'current' during early boot This logic was inherited from x86 (which was updated several times since). Unlike x86 (at the time) however, while NULL isn't mapped in ARM, 0xfffff000 is, making this actively dangerous. Drop the logic entirely, and leave 'current' as NULL during early boot. Signed-off-by: Andrew Cooper Acked-by: Julien Grall --- diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c index 3c899cd4a0..9dd3738d44 100644 --- a/xen/arch/arm/setup.c +++ b/xen/arch/arm/setup.c @@ -798,9 +798,6 @@ void __init start_xen(unsigned long boot_phys_offset, percpu_init_areas(); set_processor_id(0); /* needed early, for smp_processor_id() */ - set_current((struct vcpu *)0xfffff000); /* debug sanity */ - idle_vcpu[0] = current; - setup_virtual_regions(NULL, NULL); /* Initialize traps early allow us to get backtrace when an error occurred */ init_traps();