Jan, > EXT email: be mindful of links/attachments. > > On 18.03.2025 05:00, Anderson Choi wrote: >> xen panic is observed with the following configuration. >> >> 1. Debug xen build (CONFIG_DEBUG=y) >> 2. dom1 of an ARINC653 domain >> 3. shutdown dom1 with xl command >> >> $ xl shutdown <domain_name> >> >> (XEN) **************************************** >> (XEN) Panic on CPU 2: >> (XEN) Assertion '!in_irq() && (local_irq_is_enabled() || >> num_online_cpus() <= 1)' failed at common/xmalloc_tlsf.c:714 >> (XEN) **************************************** >> >> panic was triggered since xfree() was called with local IRQ disabled >> and therefore assertion failed. >> >> Fix this by calling xfree() after local IRQ is enabled. >> >> Fixes: 19049f8d796a sched: fix locking in a653sched_free_vdata() >> Signed-off-by: Anderson Choi <anderson.c...@boeing.com> > > Just one nit on the patch title: There's no mention at all there of which > scheduler > it is. Imo "sched" there would better be replaced by the scheduler name. > > Jan > >> --- ...
Thanks for the comment. I have just submitted patch v2 with the following title. [PATCH v2] xen/arinc653: call xfree() with local IRQ enabled Regards, Anderson
