kexec-tools/kdump.service
Coiby Xu c08e98ca14 Allow kdump.service to access LUKS volume keys
Resolves: https://issues.redhat.com/browse/RHEL-124989
Conflict: Upstream has PrivateTmp=yes removed from kdump.service.

commit 280d4b6237b1f3bcad9cfba5e51b4f55d8b718c9
Author: Coiby Xu <coxu@redhat.com>
Date:   Mon Nov 3 09:26:21 2025 +0800

    Allow kdump.service to access LUKS volume keys

    Resoles: https://issues.redhat.com/browse/RHEL-124989

    Currently kdump.service fails to read LUKS volume keys,

        kdumpctl[4001]: Nothing to read on input.
        kdumpctl[3624]: kdump: Error: Could not unlock the LUKS device.
        kdumpctl[3624]: kdump: Failed to get logon key kdump-cryptsetup:vk-eed43d84-d79f-4b6d-8159-c859bb1915ee. Run 'kdumpctl restart' manually to start kdump.
        kdumpctl[3624]: kdump: kexec: failed to prepare for a LUKS target
        kdumpctl[3624]: kdump: Starting kdump: [FAILED]
        systemd[1]: kdump.service: Main process exited, code=exited, status=1/FAILURE
        systemd[1]: kdump.service: Failed with result 'exit-code'.
        systemd[1]: Failed to start kdump.service - Crash recovery kernel arming.

    Use KeyringMode=shared to link the user keyring of root to the session
    keyring so kdump.service can access the LUKS volume keys stored in
    root's user keyring. For more details on KeyringMode, man systemd.exec.

    Fixes: d9677e17 ("Support dumping to a LUKS-encrypted target")
    Signed-off-by: Coiby Xu <coxu@redhat.com>
2025-11-07 13:54:50 +08:00

19 lines
461 B
Desktop File

[Unit]
Description=Crash recovery kernel arming
After=network.target network-online.target remote-fs.target basic.target
DefaultDependencies=no
[Service]
Type=oneshot
ExecCondition=/bin/sh -c 'grep -q -e "crashkernel" -e "fadump" /proc/cmdline'
ExecStart=/usr/bin/kdumpctl start
ExecStop=/usr/bin/kdumpctl stop
ExecReload=/usr/bin/kdumpctl reload
RemainAfterExit=yes
StartLimitInterval=0
PrivateTmp=yes
KeyringMode=shared
[Install]
WantedBy=multi-user.target