public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Cole Robinson <crobinso@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>,
	passt-dev@passt.top, "Richard W.M. Jones" <rjones@redhat.com>,
	Yumei Huang <yuhuang@redhat.com>
Subject: Re: [PATCH] isolation: keep CAP_DAC_OVERRIDE initially
Date: Tue, 7 Oct 2025 18:49:13 +0200	[thread overview]
Message-ID: <20251007184913.43e897a8@elisabeth> (raw)
In-Reply-To: <229a2d1d-f899-4eae-a23c-d0613d6f2593@redhat.com>

On Tue, 7 Oct 2025 12:43:30 -0400
Cole Robinson <crobinso@redhat.com> wrote:

> On 10/7/25 12:02 PM, Stefano Brivio wrote:
> > [Cc: Yumei as this is somewhat related to
> >  https://archives.passt.top/passt-dev/20250926011714.5978-1-yuhuang@redhat.com/,
> >  and David as he wrote most of this part]
> > 
> > On Tue,  7 Oct 2025 08:16:39 -0400
> > Cole Robinson <crobinso@redhat.com> wrote:
> >   
> >> Reproducer that I'd expect to work
> >>
> >>   $ cd $HOME
> >>   $ sudo passt --runas $UID --socket foo.sock
> >>   Failed to bind UNIX domain socket: Permission denied
> >>
> >> A more practical example is for libguestfs apps when run as user=root.
> >>
> >> + libguestfs connects to libvirt qemu:///system
> >> + libvirt qemu:///system defaults to user=qemu.
> >>   + chowns passt runtime dir to user=qemu
> >> + libguestfs instead requests the VM run as user=root
> >>   + patches in progress but we are blocked by this issue
> >> + passt is launched as root, but can't open socket in passt dir.
> >>
> >> Obviously libvirt needs improvements too.
> >> But it seems like this is a defect as well.  
> > 
> > Thanks for the patch! I think it's absolutely unproblematic to keep
> > CAP_DAC_OVERRIDE for a moment at the beginning. Did you figure out
> > exactly why it's needed by the way?
> >   
> 
> Last line in the list above should read:
> 
> + passt is launched as root, but can't open socket in passt dir
>   because it's owned by qemu.qemu

...at this point, can you perhaps come up with a complete commit message
also including the details Rich explained / reported?

No need to repost. On the other hand it's a single patch so if you
have a moment you might as well...

> 
> >> Signed-off-by: Cole Robinson <crobinso@redhat.com>  
> > 
> > Should we add:
> > 
> > Link: https://github.com/libguestfs/libguestfs/pull/218
> > 
> > ? Or it's misleading, or you omitted it for any other reason?
> >   
> 
> Works for me! I did not intentionally omit it
> 
> Thanks,
> Cole
> 

-- 
Stefano


      reply	other threads:[~2025-10-07 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07 12:16 Cole Robinson
2025-10-07 16:02 ` Stefano Brivio
2025-10-07 16:13   ` Richard W.M. Jones
2025-10-07 16:43   ` Cole Robinson
2025-10-07 16:49     ` 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=20251007184913.43e897a8@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=crobinso@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    --cc=rjones@redhat.com \
    --cc=yuhuang@redhat.com \
    /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).