From: Paul Durrant <xadimgnik@gmail.com>
To: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: David Woodhouse <dwmw@amazon.co.uk>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
David Woodhouse <dwmw2@infradead.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
Anthony Perard <anthony.perard@citrix.com>,
"open list:X86 Xen CPUs" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 3/6] xen: xenstore: add possibility to preserve owner
Date: Wed, 22 Nov 2023 17:07:27 +0000 [thread overview]
Message-ID: <c9b15b1c-e86b-45b4-b348-8c9edde5e60d@xen.org> (raw)
In-Reply-To: <20231121221023.419901-4-volodymyr_babchuk@epam.com>
On 21/11/2023 22:10, Volodymyr Babchuk wrote:
> Add option to preserve owner when creating an entry in Xen Store. This
> may be needed in cases when Qemu is working as device model in a
*may* be needed?
I don't undertstand why this patch is necessary and the commit comment
isn't really helping me.
> domain that is Domain-0, e.g. in driver domain.
>
> "owner" parameter for qemu_xen_xs_create() function can have special
> value XS_PRESERVE_OWNER, which will make specific implementation to
> get original owner of an entry and pass it back to
> set_permissions() call.
>
> Please note, that XenStore inherits permissions, so even if entry is
> newly created by, it already has the owner set to match owner of entry
> at previous level.
>
> Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>
next prev parent reply other threads:[~2023-11-22 17:08 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 22:10 [PATCH v2 0/6] xen-arm: add support for virtio-pci Volodymyr Babchuk
2023-11-21 22:10 ` [PATCH v2 1/6] hw/xen: Set XenBackendInstance in the XenDevice before realizing it Volodymyr Babchuk
2023-11-22 15:54 ` Paul Durrant
2023-11-22 17:05 ` Paul Durrant
2023-11-22 22:44 ` Woodhouse, David via
2023-11-22 23:49 ` Volodymyr Babchuk
2023-11-22 23:55 ` Woodhouse, David via
2023-11-22 22:56 ` Volodymyr Babchuk
2023-11-22 23:04 ` David Woodhouse
2023-11-23 9:29 ` Paul Durrant
2023-11-21 22:10 ` [PATCH v2 3/6] xen: xenstore: add possibility to preserve owner Volodymyr Babchuk
2023-11-22 17:07 ` Paul Durrant [this message]
2023-11-22 22:28 ` Stefano Stabellini
2023-11-22 23:01 ` David Woodhouse
2023-11-22 23:03 ` Volodymyr Babchuk
2023-11-23 1:19 ` Volodymyr Babchuk
2023-11-21 22:10 ` [PATCH v2 2/6] xen: backends: touch some XenStore nodes only if device Volodymyr Babchuk
2023-11-22 11:07 ` Philippe Mathieu-Daudé
2023-11-22 22:49 ` Volodymyr Babchuk
2023-11-22 23:19 ` David Woodhouse
2023-11-22 17:03 ` Paul Durrant
2023-11-22 22:46 ` Woodhouse, David via
2023-11-22 22:50 ` Volodymyr Babchuk
2023-11-21 22:10 ` [PATCH v2 4/6] xen_pvdev: Do not assume Dom0 when creating a directory Volodymyr Babchuk
2023-11-22 17:11 ` Paul Durrant
2023-11-22 22:29 ` Stefano Stabellini
2023-11-22 23:03 ` David Woodhouse
2023-11-22 23:09 ` Stefano Stabellini
2023-11-22 23:11 ` David Woodhouse
2023-11-22 23:20 ` Stefano Stabellini
2023-11-22 23:46 ` Volodymyr Babchuk
2023-11-23 0:07 ` Volodymyr Babchuk
2023-11-23 9:28 ` Paul Durrant
2023-11-23 10:45 ` David Woodhouse
2023-11-23 11:43 ` Volodymyr Babchuk
2023-11-23 11:51 ` David Woodhouse
2023-11-23 11:54 ` Volodymyr Babchuk
2023-11-23 11:57 ` David Woodhouse
2023-11-23 12:17 ` Volodymyr Babchuk
2023-11-23 12:27 ` David Woodhouse
2023-11-23 12:54 ` Paul Durrant
2023-11-24 0:24 ` Volodymyr Babchuk
2023-11-24 12:56 ` Alex Bennée
2023-11-21 22:10 ` [PATCH v2 6/6] xen_arm: Add virtual PCIe host bridge support Volodymyr Babchuk
2023-11-22 22:39 ` Stefano Stabellini
2023-11-22 23:44 ` Vikram Garhwal
2023-11-23 0:11 ` Volodymyr Babchuk
2023-11-24 12:30 ` Igor Mammedov
2023-11-24 15:47 ` Volodymyr Babchuk
2023-11-21 22:10 ` [PATCH v2 5/6] xen_arm: Set mc->max_cpus to GUEST_MAX_VCPUS in xen_arm_init() Volodymyr Babchuk
2023-11-22 11:10 ` Philippe Mathieu-Daudé
2023-11-24 12:04 ` Igor Mammedov
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=c9b15b1c-e86b-45b4-b348-8c9edde5e60d@xen.org \
--to=xadimgnik@gmail.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=anthony.perard@citrix.com \
--cc=dwmw2@infradead.org \
--cc=dwmw@amazon.co.uk \
--cc=eduardo@habkost.net \
--cc=julien@xen.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).