From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] rootfs: do not expose /sys/firmware while building root file-systems
Date: Thu, 7 Aug 2025 17:23:48 +0200 [thread overview]
Message-ID: <aJTFBNOxaBhG_vie@abai.de> (raw)
In-Reply-To: <20250617123507.2245-1-cedric.hombourger@siemens.com>
On 2025-06-17 14:35, 'Cedric Hombourger' via isar-users wrote:
> We need /sys while assembling the target root file-system but it exposes
> more than the build really needs. Some maintainer scripts (e.g. mdmadm)
> check /sys/firmware/efi/efivars while configuring themselves. This would
> normally be fine but for Isar builds, any information extracted from there
> is for the host doing the build and not for the target we are building for.
> In addition, packages seeing /sys/firmware/efi will mount efivars there
> and will cause do_rootfs_umount to fail unmounting /sys (because of that
> extra mount). By mounting a (small) tmpfs as /sys/firmware in the root
> file-system, we hide host details from the build; that extra mount needs
> to be removed before we attempt to unmount /sys (but we are in control).
Applied to next, thanks.
With kind regards,
Baurzhan
--
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/aJTFBNOxaBhG_vie%40abai.de.
prev parent reply other threads:[~2025-08-07 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 12:35 'Cedric Hombourger' via isar-users
2025-06-17 12:39 ` Srinuvasan Arjunan
2025-06-17 12:58 ` 'MOESSBAUER, Felix' via isar-users
2025-06-17 14:26 ` 'Jan Kiszka' via isar-users
2025-06-17 14:48 ` 'cedric.hombourger@siemens.com' via isar-users
2025-08-07 15:23 ` Baurzhan Ismagulov [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=aJTFBNOxaBhG_vie@abai.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox