From: Furkan Caliskan <frn1furkan10@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: jgross@suse.com, jbeulich@suse.com, andrew.cooper3@citrix.com,
dfaggioli@suse.com, gwd@xenproject.org,
Furkan Caliskan <frn1furkan10@gmail.com>
Subject: [PATCH 1/2] xen/sched: core: skip missing vcpu slots in sched_move_domain()
Date: Tue, 18 Aug 2026 09:32:58 +0300 [thread overview]
Message-ID: <20260818063259.18733-2-frn1furkan10@gmail.com> (raw)
In-Reply-To: <20260818063259.18733-1-frn1furkan10@gmail.com>
sched_move_domain() derives the number of units to rebuild from
d->max_vcpus, which is fixed at domain creation and never rolled
back if vcpu_create() fails partway through building a domain. So
d->vcpu[i] can be NULL for some i even though max_vcpus still
counts it - this happens if sched_alloc_udata() returns NULL.
The per-unit loop doesn't check for this: it sets
unit->vcpu_list = d->vcpu[unit_id] (NULL) and hands that broken
unit straight to the destination scheduler's alloc_udata(),
which assumes vcpu_list is always valid and crashes Xen when
it is not.
Reproduced by building a domain in a non-default cpupool where
vcpu creation fails partway through, then destroying it.
domain_kill() moves the domain back to the default cpupool via
sched_move_domain() before actually destroying it, crashing
inside the destination scheduler's alloc_udata() (seen in
Credit2's csched2_alloc_udata() -> is_idle_unit() -> NULL deref).
Before building a unit in sched_move_domain(), check that all of
its vcpu slots are populated, and skip it if any are missing. The
rest of the function walks the vcpus that actually exist, via
for_each_vcpu() rather than n_units, so skipping a unit here
does not leave anything else out of sync.
Signed-off-by: Furkan Caliskan <frn1furkan10@gmail.com>
---
xen/common/sched/core.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/xen/common/sched/core.c b/xen/common/sched/core.c
index d3a0a97e1d..d542c76543 100644
--- a/xen/common/sched/core.c
+++ b/xen/common/sched/core.c
@@ -745,6 +745,25 @@ int sched_move_domain(struct domain *d, struct cpupool *c)
for ( unit_idx = 0; unit_idx < n_units; unit_idx++ )
{
+ /*
+ * Skip this unit if any of its vcpus is missing. Bounded by
+ * max_vcpus.
+ */
+ bool vcpu_failed = false;
+
+ for ( unsigned int i = 0;
+ i < gran && unit_idx * gran + i < d->max_vcpus; i++ )
+ {
+ if ( !d->vcpu[unit_idx * gran + i] )
+ {
+ vcpu_failed = true;
+ break;
+ }
+ }
+
+ if ( vcpu_failed )
+ continue;
+
unit = sched_alloc_unit_mem();
if ( unit )
{
--
2.34.1
next prev parent reply other threads:[~2026-08-18 6:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 6:32 [PATCH 0/2] xen/sched: fix crashes when vcpu creation fails Furkan Caliskan
2026-08-18 6:32 ` Furkan Caliskan [this message]
2026-08-18 7:11 ` [PATCH 1/2] xen/sched: core: skip missing vcpu slots in sched_move_domain() Jürgen Groß
2026-08-18 7:53 ` Furkan Çalışkan
2026-08-18 10:04 ` Andrew Cooper
2026-08-18 10:13 ` Jürgen Groß
2026-08-18 10:35 ` Andrew Cooper
2026-08-18 10:47 ` Juergen Gross
2026-08-18 10:53 ` Jan Beulich
2026-08-18 12:12 ` Furkan Çalışkan
2026-08-18 12:19 ` Jan Beulich
2026-08-18 6:32 ` [PATCH 2/2] xen/sched: core: kill unarmed timers on sched_init_vcpu() failure Furkan Caliskan
2026-08-18 7:23 ` Jürgen Groß
2026-08-18 6:48 ` [PATCH 0/2] xen/sched: fix crashes when vcpu creation fails Jan Beulich
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=20260818063259.18733-2-frn1furkan10@gmail.com \
--to=frn1furkan10@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=dfaggioli@suse.com \
--cc=gwd@xenproject.org \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--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.