From: Stefano Brivio <sbrivio@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>
Cc: passt-dev@passt.top, Laine Stump <laine@redhat.com>,
Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH] contrib/selinux: Enable mapping guest memory for libvirt guests
Date: Thu, 20 Feb 2025 17:28:33 +0100 [thread overview]
Message-ID: <20250220172833.3b05c2c5@elisabeth> (raw)
In-Reply-To: <20250214143705.0ca05b19@elisabeth>
On Fri, 14 Feb 2025 14:37:05 +0100
Stefano Brivio <sbrivio@redhat.com> wrote:
> On Fri, 14 Feb 2025 05:30:44 -0800
> Andrea Bolognani <abologna@redhat.com> wrote:
>
> > On Thu, Feb 13, 2025 at 11:16:42PM +0100, Stefano Brivio wrote:
> > > This doesn't actually belong to passt's own policy: we should export
> > > an interface and libvirt's policy should use it, because passt's
> > > policy shouldn't be aware of svirt_image_t at all.
> > >
> > > However, libvirt doesn't maintain its own policy, which makes policy
> > > updates rather involved. Add this workaround to ensure --vhost-user
> > > is working in combination with libvirt, as it might take ages before
> > > we can get the proper rule in libvirt's policy.
> >
> > Is the need to update libvirt's policy for these passt changes being
> > tracked anywhere?
>
> No. :)
>
> > Because if not it will not take ages, it will simply never happen.
>
> It will happen. :)
>
> > Especially if a workaround in passt's policy effectively sweeps the
> > issue under the rug.
>
> I'll take up the rug next week. :)
Tracked at https://github.com/fedora-selinux/selinux-policy/issues/2579.
--
Stefano
prev parent reply other threads:[~2025-02-20 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 22:16 [PATCH] contrib/selinux: Enable mapping guest memory for libvirt guests Stefano Brivio
2025-02-14 13:30 ` Andrea Bolognani
2025-02-14 13:37 ` Stefano Brivio
2025-02-20 16:28 ` Stefano Brivio [this message]
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=20250220172833.3b05c2c5@elisabeth \
--to=sbrivio@redhat.com \
--cc=abologna@redhat.com \
--cc=laine@redhat.com \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).