From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH 5/8] host/rootfs: create a per-VM user namespace
Date: Thu, 11 Dec 2025 13:41:49 +0100 [thread overview]
Message-ID: <87tsxx5gxe.fsf@alyssa.is> (raw)
In-Reply-To: <dea7d1f6-c56b-4df7-86c6-1f495d52f0f8@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2205 bytes --]
Demi Marie Obenour <demiobenour@gmail.com> writes:
> On 12/10/25 07:47, Alyssa Ross wrote:
>> The document portal has to be root to mount its fuse filesystem. This
>> needs to be a shared namespace because virtiofsd needs to be in the
>> same mount namespace as the document portal so that it sees the fuse
>> filesystem, so we create a per-VM persistent user namespace.
>>
>> Signed-off-by: Alyssa Ross <hi@alyssa.is>
>
> (snip)
>
>> diff --git a/host/rootfs/image/usr/bin/run-appimage b/host/rootfs/image/usr/bin/run-appimage
>> index 47cab4c5..5e8e29fa 100755
>> --- a/host/rootfs/image/usr/bin/run-appimage
>> +++ b/host/rootfs/image/usr/bin/run-appimage
>> @@ -44,4 +44,6 @@ if { s6-instance-delete /run/service/vm-services $id }
>>
>> if { umount ${dir}/mount } # mount namespace
>> if { umount ${dir}/mount } # private bind mount
>> +if { umount ${dir}/user } # user namespace
>> +if { umount ${dir}/user } # private bind mount
>> rm -r $dir /run/configs/${id}
>> diff --git a/host/rootfs/image/usr/bin/run-flatpak b/host/rootfs/image/usr/bin/run-flatpak
>> index bb366735..86ccc12a 100755
>> --- a/host/rootfs/image/usr/bin/run-flatpak
>> +++ b/host/rootfs/image/usr/bin/run-flatpak
>> @@ -46,4 +46,6 @@ if { s6-instance-delete -- /run/service/vm-services $id }
>>
>> if { umount ${dir}/mount } # mount namespace
>> if { umount ${dir}/mount } # private bind mount
>> +if { umount ${dir}/user } # user namespace
>> +if { umount ${dir}/user } # private bind mount
>> rm -r $dir /run/configs/${id}
>
> Why is it necessary to unmount twice here?
Because we mount twice, just like the comments say. It is a bit
counterintuitive though. Namespaces can only be mounted onto a
mountpoint that itself has private propagation. This is why we create a
private bind mount at the start of create-vm-dependencies before unshare
bind mounts the namespaces. You can also see this in an example in
unshare(1).
Perhaps it would be better and clearer to have /run/vm/by-id/${VM}/ns as
a private mountpoint, with the nsfs files inside? That way, each of
them only needs to be unmounted once, and then the ns directory also has
to be unmounted once.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2025-12-11 12:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 12:47 [PATCH 1/8] host/rootfs: create dbus socket externally Alyssa Ross
2025-12-10 12:47 ` [PATCH 2/8] host/rootfs: move vsock sockets out of VM dir Alyssa Ross
2025-12-10 12:47 ` [PATCH 3/8] host/rootfs: move portal bus socket " Alyssa Ross
2025-12-10 12:47 ` [PATCH 4/8] host/rootfs: run xdg-desktop-portal-spectrum-host as non-root Alyssa Ross
2025-12-10 17:26 ` Demi Marie Obenour
2025-12-11 12:19 ` Alyssa Ross
2025-12-11 14:05 ` Alyssa Ross
2025-12-12 17:54 ` Demi Marie Obenour
2025-12-10 12:47 ` [PATCH 5/8] host/rootfs: create a per-VM user namespace Alyssa Ross
2025-12-10 17:39 ` Demi Marie Obenour
2025-12-11 12:41 ` Alyssa Ross [this message]
2025-12-12 17:51 ` Demi Marie Obenour
2025-12-12 17:56 ` Alyssa Ross
2025-12-10 12:47 ` [PATCH 6/8] host/rootfs: move xdp runtime dir out of VM dir Alyssa Ross
2025-12-10 17:43 ` Demi Marie Obenour
2025-12-11 12:47 ` Alyssa Ross
2025-12-11 13:06 ` Alyssa Ross
2025-12-10 12:47 ` [PATCH 7/8] host/rootfs: move fs directory out of VM directory Alyssa Ross
2025-12-10 12:47 ` [PATCH 8/8] host/rootfs: run filesystem daemons as non-root Alyssa Ross
2025-12-10 18:29 ` Demi Marie Obenour
2025-12-11 12:46 ` Alyssa Ross
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=87tsxx5gxe.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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).