From: Jason Andryuk <jason.andryuk@amd.com>
To: Juergen Gross <jgross@suse.com>, <xen-devel@lists.xenproject.org>
Cc: Julien Grall <julien@xen.org>,
Anthony PERARD <anthony.perard@vates.tech>
Subject: Re: [PATCH v2 4/4] tools/xenstored: remove permissions related to dead domain
Date: Wed, 29 Apr 2026 12:41:22 -0400 [thread overview]
Message-ID: <e9cfb86e-704d-4a5d-bc59-ad05d07bf69a@amd.com> (raw)
In-Reply-To: <20260429120619.1013440-5-jgross@suse.com>
On 2026-04-29 08:06, Juergen Gross wrote:
> Wit unprivileged domains now capable to use the @releaseDomain watch,
s/Wit/With/ again.
Regards,
Jason
> there is no reason not to remove any node permissions which relate to
> a domain which has been removed.
>
> This resolves a complex scenario where a new domain could inherit the
> permissions of an old one with the same domid.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> Reviewed-by: Jason Andryuk <jason.andryuk@amd.com>
next prev parent reply other threads:[~2026-04-29 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 12:06 [PATCH v2 0/4] tools/xenstore: fix issue related to XSA-417 Juergen Gross
2026-04-29 12:06 ` [PATCH v2 1/4] xen/public: introduce DOMID_ANY Juergen Gross
2026-05-14 1:15 ` Stefano Stabellini
2026-04-29 12:06 ` [PATCH v2 2/4] tools/xenstored: add support for "all domains" node permission Juergen Gross
2026-04-29 12:06 ` [PATCH v2 3/4] tools/xenstored: allow @releaseDomain watch for all domains Juergen Gross
2026-04-29 12:06 ` [PATCH v2 4/4] tools/xenstored: remove permissions related to dead domain Juergen Gross
2026-04-29 16:41 ` Jason Andryuk [this message]
2026-05-07 7:43 ` Jürgen Groß
2026-05-07 7:53 ` Jan Beulich
2026-05-12 15:48 ` [PATCH v2 0/4] tools/xenstore: fix issue related to XSA-417 Oleksii Kurochko
2026-05-12 15:52 ` Jürgen Groß
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=e9cfb86e-704d-4a5d-bc59-ad05d07bf69a@amd.com \
--to=jason.andryuk@amd.com \
--cc=anthony.perard@vates.tech \
--cc=jgross@suse.com \
--cc=julien@xen.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.