From: Norbert Lange <nolange79@gmail.com>
To: buildroot@buildroot.org
Cc: Norbert Lange <nolange79@gmail.com>,
jeremy.rosen@smile.fr, yann.morin.1998@free.fr,
maxime.hadjinlian@gmail.com
Subject: [Buildroot] [PATCH v3] package/systemd: invoke systemd-tmpfilesd on final image
Date: Sun, 9 Jan 2022 12:07:35 +0100 [thread overview]
Message-ID: <20220109110736.3963-1-nolange79@gmail.com> (raw)
Especially for read-only filesystems it is helpfull to
pre-create all folders for non-volatile paths.
This needs to run under fakeroot to allow setting
uids/gids/perms for the target fs.
systemd-tmpfilesd supports specifiers and target rootfs,
but some specifiers resolve to information from the host,
it is necessary to specially handle (skip) entries that
contain problematic specifiers.
Signed-off-by: Norbert Lange <nolange79@gmail.com>
---
v1->v2
* add a script to skip/handle specifiers that might
otherwise take information from the host
v2->v3
* adopt fakeroot_tmpfiles.sh to current systemd-tmpfilesd (v250),
several more specifiers are supported directly for our usecase.
---
package/systemd/fakeroot_tmpfiles.sh | 57 ++++++++++++++++++++++++++++
package/systemd/systemd.mk | 9 ++++-
2 files changed, 64 insertions(+), 2 deletions(-)
create mode 100644 package/systemd/fakeroot_tmpfiles.sh
diff --git a/package/systemd/fakeroot_tmpfiles.sh b/package/systemd/fakeroot_tmpfiles.sh
new file mode 100644
index 0000000000..7e9b02cc0a
--- /dev/null
+++ b/package/systemd/fakeroot_tmpfiles.sh
@@ -0,0 +1,57 @@
+#!/bin/sh
+#
+# The systemd-tmpfiles has the ability to grab information
+# from the filesystem (instead from the running system).
+#
+# However there are a few specifiers that *always* will grab
+# information from the running system examples are %a, %b, %m, %H
+# (Architecture, Boot UUID, Machine UUID, Hostname).
+#
+# See [1] for historic information.
+#
+# This script will (conservatively) skip tmpfiles lines that have
+# such an specifier to prevent leaking host information.
+#
+# shell expansion is critical to be POSIX compliant,
+# this script wont work with zsh in its default mode for example.
+#
+# The script takes several measures to handle more complex stuff
+# like passing this correctly:
+# f+ "/var/example" - - - - %B\n%o\n%w\n%W%%\n
+#
+# [1] - https://github.com/systemd/systemd/pull/16187
+
+[ -n "${HOST_SYSTEMD_TMPFILES-}" ] ||
+ HOST_SYSTEMD_TMPFILES=systemd-tmpfiles
+
+[ -n "${1-}" -a -d "${1-}"/usr/lib/tmpfiles.d ] ||
+ { echo 1>&2 "$0: need ROOTFS argument"; exit 1; }
+
+${HOST_SYSTEMD_TMPFILES} --no-pager --cat-config --root="$1" |
+ sed -e '/^[[:space:]]*#/d' -e 's,^[[:space:]]*,,' -e '/^$/d' |
+ while read -r line; do
+ # it is allowed to use quotes around arguments,
+ # so let the shell pack the arguments
+ eval "set -- $line"
+
+ # dont output warnings for directories we dont process
+ [ "${2#/dev}" = "${2}" ] && [ "${2#/proc}" = "${2}" ] &&
+ [ "${2#/run}" = "${2}" ] && [ "${2#/sys}" = "${2}" ] &&
+ [ "${2#/tmp}" = "${2}" ] && [ "${2#/mnt}" = "${2}" ] ||
+ continue
+
+ # blank out all specs that are ok to use,
+ # test if some remain. (Specs up to date with v250)
+ if echo "$2 ${7-}" | sed -e 's,%[%BCEgGhLMosStTuUVwW],,g' | grep -v -q '%'; then
+ # no "bad" specifiers, pass the line unmodified
+ eval "printf '%s\n' '$line'"
+ else
+ # warn
+ eval "printf 'ignored spec: %s\n' '$line' 1>&2"
+ fi
+ done |
+\
+TMPDIR= TEMP= TMP= ${HOST_SYSTEMD_TMPFILES} --create --boot --root="$1" \
+ --exclude-prefix=/dev --exclude-prefix=/proc --exclude-prefix=/run --exclude-prefix=/sys \
+ --exclude-prefix=/tmp --exclude-prefix=/mnt \
+ -
diff --git a/package/systemd/systemd.mk b/package/systemd/systemd.mk
index 7bf8018438..e136229c8e 100644
--- a/package/systemd/systemd.mk
+++ b/package/systemd/systemd.mk
@@ -709,10 +709,15 @@ define SYSTEMD_RM_CATALOG_UPDATE_SERVICE
endef
SYSTEMD_ROOTFS_PRE_CMD_HOOKS += SYSTEMD_RM_CATALOG_UPDATE_SERVICE
+define SYSTEMD_CREATE_TMPFILES_HOOK
+ HOST_SYSTEMD_TMPFILES=$(HOST_DIR)/bin/systemd-tmpfiles \
+ /bin/sh $(SYSTEMD_PKGDIR)/fakeroot_tmpfiles.sh $(TARGET_DIR)
+endef
+
define SYSTEMD_PRESET_ALL
$(HOST_DIR)/bin/systemctl --root=$(TARGET_DIR) preset-all
endef
-SYSTEMD_ROOTFS_PRE_CMD_HOOKS += SYSTEMD_PRESET_ALL
+SYSTEMD_ROOTFS_PRE_CMD_HOOKS += SYSTEMD_CREATE_TMPFILES_HOOK SYSTEMD_PRESET_ALL
SYSTEMD_CONF_ENV = $(HOST_UTF8_LOCALE_ENV)
SYSTEMD_NINJA_ENV = $(HOST_UTF8_LOCALE_ENV)
@@ -783,7 +788,7 @@ HOST_SYSTEMD_CONF_OPTS = \
-Dvconsole=false \
-Dquotacheck=false \
-Dsysusers=false \
- -Dtmpfiles=false \
+ -Dtmpfiles=true \
-Dimportd=false \
-Dhwdb=false \
-Drfkill=false \
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-01-09 11:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 11:07 Norbert Lange [this message]
2022-01-09 14:49 ` [Buildroot] [PATCH v3] package/systemd: invoke systemd-tmpfilesd on final image Arnout Vandecappelle
2022-01-09 21:01 ` Norbert Lange
2022-01-09 14:49 ` Arnout Vandecappelle
2022-07-04 6:41 ` yann.morin
[not found] ` <20220704064121.GA2889@tl-lnx-nyma7486>
2022-07-04 6:45 ` yann.morin
2022-07-04 11:05 ` Norbert Lange
2022-07-04 12:07 ` yann.morin
2022-07-04 15:57 ` Norbert Lange
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=20220109110736.3963-1-nolange79@gmail.com \
--to=nolange79@gmail.com \
--cc=buildroot@buildroot.org \
--cc=jeremy.rosen@smile.fr \
--cc=maxime.hadjinlian@gmail.com \
--cc=yann.morin.1998@free.fr \
/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