mirror of
https://github.com/systemd/systemd
synced 2024-10-15 12:34:37 +00:00
1fb7f8e15e
This should cover cases regarding devices with `OPTIONS+="db_persist"` during initrd->sysroot transition. See: * https://github.com/systemd/systemd/issues/23429 * https://github.com/systemd/systemd/pull/23218 * https://github.com/systemd/systemd/pull/23489 * https://bugzilla.redhat.com/show_bug.cgi?id=2087225
89 lines
2.6 KiB
Bash
Executable file
89 lines
2.6 KiB
Bash
Executable file
#!/usr/bin/env bash
|
|
# SPDX-License-Identifier: LGPL-2.1-or-later
|
|
set -e
|
|
|
|
TEST_DESCRIPTION="cryptsetup systemd setup"
|
|
IMAGE_NAME="cryptsetup"
|
|
TEST_NO_NSPAWN=1
|
|
TEST_FORCE_NEWIMAGE=1
|
|
|
|
# shellcheck source=test/test-functions
|
|
. "${TEST_BASE_DIR:?}/test-functions"
|
|
|
|
PART_UUID="deadbeef-dead-dead-beef-000000000000"
|
|
DM_NAME="test24_varcrypt"
|
|
# Mount the keyfile only in initrd (hence rd.luks.key), since it resides on
|
|
# the rootfs and we would get a (harmless) error when trying to mount it after
|
|
# switching root (since rootfs is already mounted)
|
|
KERNEL_APPEND+=" rd.luks=1 luks.name=$PART_UUID=$DM_NAME rd.luks.key=$PART_UUID=/etc/varkey:LABEL=systemd_boot"
|
|
|
|
check_result_qemu() {
|
|
local ret=1
|
|
|
|
mount_initdir
|
|
[[ -e "${initdir:?}/testok" ]] && ret=0
|
|
[[ -f "$initdir/failed" ]] && cp -a "$initdir/failed" "${TESTDIR:?}"
|
|
|
|
cryptsetup luksOpen "${LOOPDEV:?}p2" "${DM_NAME:?}" <"$TESTDIR/keyfile"
|
|
mount "/dev/mapper/$DM_NAME" "$initdir/var"
|
|
save_journal "$initdir/var/log/journal"
|
|
check_coverage_reports "${initdir:?}" || ret=5
|
|
_umount_dir "$initdir/var"
|
|
_umount_dir "$initdir"
|
|
cryptsetup luksClose "/dev/mapper/$DM_NAME"
|
|
|
|
[[ -f "$TESTDIR/failed" ]] && cat "$TESTDIR/failed"
|
|
echo "${JOURNAL_LIST:-No journals were saved}"
|
|
|
|
test -s "$TESTDIR/failed" && ret=1
|
|
return $ret
|
|
}
|
|
|
|
test_create_image() {
|
|
create_empty_image_rootdir
|
|
|
|
echo -n test >"${TESTDIR:?}/keyfile"
|
|
cryptsetup -q luksFormat --uuid="$PART_UUID" --pbkdf pbkdf2 --pbkdf-force-iterations 1000 "${LOOPDEV:?}p2" "$TESTDIR/keyfile"
|
|
cryptsetup luksOpen "${LOOPDEV}p2" "${DM_NAME:?}" <"$TESTDIR/keyfile"
|
|
mkfs.ext4 -L var "/dev/mapper/$DM_NAME"
|
|
mkdir -p "${initdir:?}/var"
|
|
mount "/dev/mapper/$DM_NAME" "$initdir/var"
|
|
|
|
LOG_LEVEL=5
|
|
|
|
setup_basic_environment
|
|
mask_supporting_services
|
|
|
|
install_dmevent
|
|
generate_module_dependencies
|
|
|
|
echo -n test >"$initdir/etc/varkey"
|
|
|
|
cat >>"$initdir/etc/fstab" <<EOF
|
|
/dev/mapper/$DM_NAME /var ext4 defaults 0 1
|
|
EOF
|
|
|
|
# Forward journal messages to the console, so we have something
|
|
# to investigate even if we fail to mount the encrypted /var
|
|
echo ForwardToConsole=yes >> "$initdir/etc/systemd/journald.conf"
|
|
}
|
|
|
|
cleanup_root_var() {
|
|
ddebug "umount ${initdir:?}/var"
|
|
mountpoint "$initdir/var" && umount "$initdir/var"
|
|
[[ -b "/dev/mapper/${DM_NAME:?}" ]] && cryptsetup luksClose "/dev/mapper/$DM_NAME"
|
|
}
|
|
|
|
test_cleanup() {
|
|
# ignore errors, so cleanup can continue
|
|
cleanup_root_var || :
|
|
_test_cleanup
|
|
}
|
|
|
|
test_setup_cleanup() {
|
|
cleanup_root_var || :
|
|
cleanup_initdir
|
|
}
|
|
|
|
do_test "$@"
|