From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Cc: ulrich.teichert@ebs-group.io, florian.bezdeka@siemens.com,
cedric.hombourger@siemens.com
Subject: Re: [PATCH 1/1] rootfs: restore compatibility with bwrap 0.12.0
Date: Fri, 4 Sep 2026 10:32:29 +0200 [thread overview]
Message-ID: <d813f511-e7d8-4cb7-b3b1-d004915ef570@ilbers.de> (raw)
In-Reply-To: <20260831084200.751483-1-felix.moessbauer@siemens.com>
Applied to next, thanks.
Zhihang
On 8/31/26 10:42, 'Felix Moessbauer' via isar-users wrote:
> Bubblewrap 0.12.0 is a security release that contains hardenings
> regarding the handling of symlinks. This breaks the rootfs_cmd helper,
> which over-mounts /bin, /lib and /lib64, which are symlinks to /usr/bin
> (and alike).
>
> From debian bookworm on, /bin (and alike) are just symlinks to the
> corresponding dirs below /usr. In this case, we only need to mount /usr.
> On earlier versions, we need to mount the /bin (and alike) dirs as well.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> meta/classes-recipe/rootfs.bbclass | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes-recipe/rootfs.bbclass b/meta/classes-recipe/rootfs.bbclass
> index 8d394b05..0bef2d45 100644
> --- a/meta/classes-recipe/rootfs.bbclass
> +++ b/meta/classes-recipe/rootfs.bbclass
> @@ -142,8 +142,9 @@ rootfs_cmd() {
> fi
> shift # remove "--", command and its arguments follows
>
> + # bin, lib and lib64 are only real directories on unmerged-usr rootfs
> for ro_d in bin etc lib lib64 sys usr var; do
> - [ -d ${bwrap_rootfs}/${ro_d} ] || continue
> + [ -d ${bwrap_rootfs}/${ro_d} ] && [ ! -L ${bwrap_rootfs}/${ro_d} ] || continue
> bwrap_args="${bwrap_args} --ro-bind ${bwrap_rootfs}/${ro_d} /${ro_d}"
> done
>
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/d813f511-e7d8-4cb7-b3b1-d004915ef570%40ilbers.de.
prev parent reply other threads:[~2026-09-04 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 8:42 'Felix Moessbauer' via isar-users
2026-08-31 13:44 ` 'Ulrich Teichert' via isar-users
2026-09-04 8:32 ` Zhihang Wei [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=d813f511-e7d8-4cb7-b3b1-d004915ef570@ilbers.de \
--to=wzh@ilbers.de \
--cc=cedric.hombourger@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ulrich.teichert@ebs-group.io \
/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