From: Jan Beulich <jbeulich@suse.com>
To: dmkhn@proton.me
Cc: andrew.cooper3@citrix.com, anthony.perard@vates.tech,
julien@xen.org, michal.orzel@amd.com, roger.pau@citrix.com,
sstabellini@kernel.org, dmukhin@ford.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v6 2/2] xen/domain: adjust domain ID allocation for Arm
Date: Sun, 18 May 2025 10:57:44 +0200 [thread overview]
Message-ID: <bbbf5488-e501-4e1d-8eff-c703e55f4456@suse.com> (raw)
In-Reply-To: <20250516020434.1145337-3-dmukhin@ford.com>
On 16.05.2025 04:04, dmkhn@proton.me wrote:
> --- a/xen/common/domain.c
> +++ b/xen/common/domain.c
> @@ -85,7 +85,7 @@ void __init domid_init(void)
> *
> * If hint is outside of valid [0..DOMID_FIRST_RESERVED - 1] range of IDs,
> * perform an exhaustive search starting from the end of the used domain ID
> - * range.
> + * range, excluding get_initial_domain_id() ID.
> */
> domid_t domid_alloc(domid_t domid)
> {
> @@ -103,6 +103,9 @@ domid_t domid_alloc(domid_t domid)
> if ( domid == DOMID_FIRST_RESERVED )
> domid = 0;
>
> + if ( domid == get_initial_domain_id() )
> + continue;
> +
> if ( !rangeset_contains_singleton(domid_rangeset, domid) )
> break;
> }
Isn't there a (perhaps even pre-existing) issue here with a DomU potentially
getting ID 0 assigned when get_initial_domain_id() returns non-zero?
Jan
next prev parent reply other threads:[~2025-05-18 8:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 2:04 [PATCH v6 0/2] xen/domain: domain ID allocation dmkhn
2025-05-16 2:04 ` [PATCH v6 1/2] xen/domain: unify " dmkhn
2025-05-16 8:43 ` Teddy Astie
2025-05-16 18:06 ` dmkhn
2025-05-16 20:35 ` Julien Grall
2025-05-16 21:14 ` dmkhn
2025-05-18 8:52 ` Jan Beulich
2025-05-19 19:31 ` dmkhn
2025-05-16 2:04 ` [PATCH v6 2/2] xen/domain: adjust domain ID allocation for Arm dmkhn
2025-05-18 8:57 ` Jan Beulich [this message]
2025-05-19 19:28 ` dmkhn
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=bbbf5488-e501-4e1d-8eff-c703e55f4456@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=dmkhn@proton.me \
--cc=dmukhin@ford.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.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.