From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH 3/3] host/rootfs: add run-flatpak script
Date: Mon, 24 Nov 2025 16:25:35 +0100 [thread overview]
Message-ID: <87cy57311s.fsf@alyssa.is> (raw)
In-Reply-To: <06f57b2f-97c7-42bf-97e1-a7abe4a5254d@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2226 bytes --]
Demi Marie Obenour <demiobenour@gmail.com> writes:
> On 11/13/25 07:04, Alyssa Ross wrote:
>> +# SPDX-License-Identifier: EUPL-1.2+
>> +# SPDX-FileCopyrightText: 2024 Alyssa Ross <hi@alyssa.is>
>> +
>> +backtick -E dir { mktemp -d /run/vm/by-id/XXXXXX }
>> +backtick -E id { basename -- $dir }
>
> Serial substitution: if $1 or $2 contains something like ${dir} or ${id}
> they will be expanded again. Can be avoided with multisubstitute:
>
> backtick dir { mktemp -d /run/vm/by-id/XXXXXX }
> backtick id { importas -iS dir basename -- $dir }
> multisubstitute {
> import -iS dir
> import -iS id
> define install_dir $1
> define app_id $2
> }
>
> The general rule I follow is to never substitute a parameter into
> an argv that has already been substituted into. This can be done
> by renaming all "variables" whenever one does a substitution.
>
>> +if { mkdir -p /run/configs/${id}/fs }
>> +if { redirfd -w 1 /run/configs/${id}/fs/type echo flatpak }
>> +if { cd /run/configs/${id}/fs mount-flatpak $1 $2 }
>> +if {
>> + ln -s /usr/lib/spectrum/img/appvm/blk /usr/lib/spectrum/img/appvm/vmlinux
>> + /run/configs/${id}
>> +}
>> +
>> +if { ln -s /run/configs/${id} ${dir}/config }
>> +
>> +if { create-vm-dependencies $id }
>> +
>> +piperw 4 3
>> +background {
>> + fdclose 3
>> + fdmove 0 4
>> +
>> + # Wait for the VMM to be up, then start the VM.
>> + if { redirfd -w 1 /dev/null head -1 }
>> + vm-start $id
>> +}
>> +fdclose 4
>> +
>> +foreground { run-vmm $id }
>> +fdclose 3
>> +
>> +if {
>> + forx -pE service {
>> + dbus
>> + vhost-user-fs
>> + vhost-user-gpu
>> + xdg-desktop-portal-spectrum-host
>> + }
>> + s6-instance-delete /run/service/${service} $id
>> +}
>
> Serial substitution again. This should not be an issue: POSIX requires
> mktemp to use only characters in the portable filename character set,
> and $ is not in that set. An execline static analyzer would flag
> this, though.
>
> If you want to avoid serial substitution, the usual workaround of
> multisubstitute should do the job.
>
Minor correction: POSIX doesn't specify mktemp(1), only the library
functions, but Busybox mktemp uses mkdtemp(3), which is also specified
to use the portable character set.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2025-11-24 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 12:04 [PATCH 1/3] tools/mount-flatpak: init Alyssa Ross
2025-11-13 12:04 ` [PATCH 2/3] img/app: run Flatpak applications Alyssa Ross
2025-11-13 12:04 ` [PATCH 3/3] host/rootfs: add run-flatpak script Alyssa Ross
2025-11-14 19:36 ` Demi Marie Obenour
2025-11-24 15:25 ` Alyssa Ross [this message]
2025-11-13 19:25 ` [PATCH 1/3] tools/mount-flatpak: init Demi Marie Obenour
2025-11-14 11:12 ` Alyssa Ross
2025-11-14 22:52 ` Demi Marie Obenour
2025-11-15 12:00 ` Alyssa Ross
2025-11-15 12:01 ` Alyssa Ross
2025-11-18 1:37 ` Demi Marie Obenour
2025-11-14 19:11 ` Demi Marie Obenour
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=87cy57311s.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).