Support kdump with LUKS encryption by reusing LUKS volume keys
Subsystems (6)
v8 cover Support kdump with LUKS encryption by reusing LUKS volume keys
LUKS is the standard for Linux disk encryption, widely adopted by users, and in some cases, such as Confidential VMs, it is a requirement. With kdump enabled, when the first kernel crashes, the system can boot into the kdump/crash kernel to dump the memory image (i.e., /proc/vmcore) to a specified target. However, there are two challenges when dumping vmcore to a LUKS-encrypted device:
- Kdump kernel may not be able to decrypt the LUKS partition. For some machines, a system administrator may not have a chance to enter the password to decrypt the device in kdump initramfs after the 1st kernel crashes; For cloud confidential VMs, depending on the policy the kdump kernel may not be able to unseal the keys with TPM and the console virtual keyboard is untrusted.
- LUKS2 by default use the memory-hard Argon2 key derivation function which is quite memory-consuming compared to the limited memory reserved for kdump. Take Fedora example, by default, only 256M is reserved for systems having memory between 4G-64G. With LUKS enabled, ~1300M needs to be reserved for kdump. Note if the memory reserved for kdump can't be used by 1st kernel i.e. an user sees ~1300M memory missing in the 1st kernel.
Besides users (at least for Fedora) usually expect kdump to work out of the box i.e. no manual password input or custom crashkernel value is needed. And it doesn't make sense to derivate the keys again in kdump kernel which seems to be redundant work.
This patch set addresses the above issues by making the LUKS volume keys persistent for kdump kernel with the help of cryptsetup's new APIs (--link-vk-to-keyring/--volume-key-keyring). Here is the life cycle of the kdump copies of LUKS volume keys,
1. After the 1st kernel loads the initramfs during boot, systemd use an user-input passphrase to de-crypt the LUKS volume keys or TPM-sealed key and then save the volume keys to specified keyring (using the --link-vk-to-keyring API) and the key will expire within specified time.
2. A user space tool (kdump initramfs loader like kdump-utils) create key items inside /sys/kernel/config/crash_dm_crypt_keys to inform the 1st kernel which keys are needed.
3. When the kdump initramfs is loaded by the kexec_file_load syscall, the 1st kernel will iterate created key items, save the keys to kdump reserved memory.
4. When the 1st kernel crashes and the kdump initramfs is booted, the kdump initramfs asks the kdump kernel to create a user key using the key stored in kdump reserved memory by writing yes to /sys/kernel/crash_dm_crypt_keys/restore. Then the LUKS encrypted device is unlocked with libcryptsetup's --volume-key-keyring API.
5. The system gets rebooted to the 1st kernel after dumping vmcore to the LUKS encrypted device is finished
After libcryptsetup saving the LUKS volume keys to specified keyring, whoever takes this should be responsible for the safety of these copies of keys. The keys will be saved in the memory area exclusively reserved for kdump where even the 1st kernel has no direct access. And further more, two additional protections are added,
- save the copy randomly in kdump reserved memory as suggested by Jan
- clear the _PAGE_PRESENT flag of the page that stores the copy as suggested by Pingfan
This patch set only supports x86. There will be patches to support other architectures once this patch set gets merged.
v8
- improve documentation [Randy]
- rebase onto 6.14.0-rc1
v7
- Baoquan
- differentiate between failing to get dm crypt keys and no dm crypt keys
- add code comments, change function name and etc. to improve code readability
- add documentation for configfs API [Dave]
- fix building error found by kernel test robot
v6
- Baoquan
- support AMD SEV
- drop uncessary keys_header_size
- improve commit message of [PATCH 4/7]
- Greg
- switch to configfs
- move ifdef from .c to .h files and rework kexec_random_start
- use tab instead of space for appended code comment
- Process key description in a more flexible way to address problems found by Ondrej
- improve cover letter
- fix an compilation error as found by kernel test robot
v5
- Baoquan
- limit the feature of placing kexec_buf randomly to kdump (CONFIG_CRASH_DUMP)
- add documentation for added sysfs API
- allow to re-send init command to support the case of user switching to a different LUKS-encrypted target
- make CONFIG_CRASH_DM_CRYPT depends on CONFIG_DM_CRYPT
- check if the number of keys exceed KEY_NUM_MAX
- rename (struct keys_header).key_count as (struct keys_header).total_keys to improve code readability
- improve commit message
- fix the failure of calling crash_exclude_mem_range (there is a split of mem_range)
- use ret instead of r as return code
- Greg
- add documentation for added sysfs API
- avoid spamming kernel logs
- fix a buffer overflow issue
- keep the state enums synced up with the string values
- use sysfs_emit other than sprintf
- explain KEY_NUM_MAX and KEY_SIZE_MAX
- s/EXPORT_SYMBOL_GPL/EXPORT_SYMBOL/g
- improve code readability
- Rebase onto latest Linus tree
v4
- rebase onto latest Linus tree so Baoquan can apply the patches for code review
- fix kernel test robot warnings
v3
- Support CPU/memory hot-plugging [Baoquan]
- Don't save the keys temporarily to simplify the implementation [Baoquan]
- Support multiple LUKS encrypted volumes
- Read logon key instead of user key to improve security [Ondrej]
- A kernel config option CRASH_DM_CRYPT for this feature (disabled by default)
- Fix warnings found by kernel test robot
- Rebase the code onto 6.9.0-rc5+
v2
- work together with libscryptsetup's --link-vk-to-keyring/--volume-key-keyring APIs [Milan and Ondrej]
- add the case where console virtual keyboard is untrusted for confidential VM
- use dm_crypt_key instead of LUKS volume key [Milan and Eric]
- fix some code format issues
- don't move "struct kexec_segment" declaration
- Rebase the code onto latest Linus tree (6.7.0)
v1
- "Put the luks key handling related to crash_dump out into a separate file kernel/crash_dump_luks.c" [Baoquan]
- Put the generic luks handling code before the x86 specific code to make it easier for other arches to follow suit [Baoquan]
- Use phys_to_virt instead of "pfn -> page -> vaddr" [Dave Hansen]
- Drop the RFC prefix [Dave Young]
- Rebase the code onto latest Linus tree (6.4.0-rc4)
RFC v2
- libcryptsetup interacts with the kernel via sysfs instead of "hacking" dm-crypt
- to save a kdump copy of the LUKS volume key in 1st kernel
- to add a logon key using the copy for libcryptsetup in kdump kernel [Milan]
- to avoid the incorrect usage of LUKS master key in dm-crypt [Milan]
- save the kdump copy of LUKS volume key randomly [Jan]
- mark the kdump copy inaccessible [Pingfan]
- Miscellaneous
- explain when operations related to the LUKS volume key happen [Jan]
- s/master key/volume key/g
- use crash_ instead of kexec_ as function prefix
- fix commit subject prefixes e.g. "x86, kdump" to x86/crash
Coiby Xu (7):
kexec_file: allow to place kexec_buf randomly
crash_dump: make dm crypt keys persist for the kdump kernel
crash_dump: store dm crypt keys in kdump reserved memory
crash_dump: reuse saved dm crypt keys for CPU/memory hot-plugging
crash_dump: retrieve dm crypt keys in kdump kernel x86/crash: pass dm crypt keys to kdump kernel
x86/crash: make the page that stores the dm crypt keys inaccessible
Documentation/admin-guide/kdump/kdump.rst | 32 ++ arch/x86/kernel/crash.c | 26 +- arch/x86/kernel/kexec-bzimage64.c | 11 + arch/x86/kernel/machine_kexec_64.c | 22 ++ include/linux/crash_core.h | 7 +- include/linux/crash_dump.h | 2 + include/linux/kexec.h | 34 ++ kernel/Kconfig.kexec | 10 + kernel/Makefile | 1 + kernel/crash_dump_dm_crypt.c | 459 ++++++++++++++++++++++ kernel/kexec_file.c | 3 + 11 files changed, 604 insertions(+), 3 deletions(-) create mode 100644 kernel/crash_dump_dm_crypt.c
base-commit: bb066fe812d6fb3a9d01c073d9f1e2fd5a63403b
Signature · 1 line
2.48.1
PATCH v8 1/7 kexec_file: allow to place kexec_buf randomly
Currently, kexec_buf is placed in order which means for the same machine, the info in the kexec_buf is always located at the same position each time the machine is booted. This may cause a risk for sensitive information like LUKS volume key. Now struct kexec_buf has a new field random which indicates it's supposed to be placed in a random position.
Note this feature is enabled only when CONFIG_CRASH_DUMP is enabled. So it only takes effect for kdump and won't impact kexec reboot.
--- include/linux/kexec.h | 30 ++++++++++++++++++++++++++++++ kernel/kexec_file.c | 3 +++ 2 files changed, 33 insertions(+)
include/linux/kexec.h +30 -0
@@ -25,6 +25,10 @@extern note_buf_t __percpu *crash_notes; +#ifdef CONFIG_CRASH_DUMP +#include <linux/prandom.h> +#endif +#ifdef CONFIG_KEXEC_CORE #include <linux/list.h> #include <linux/compat.h>
@@ -171,6 +175,7 @@ int kexec_image_post_load_cleanup_default(struct kimage *image);* @buf_min: The buffer can't be placed below this address. * @buf_max: The buffer can't be placed above this address. * @top_down: Allocate from top of memory. +* @random: Place the buffer at a random position. */ struct kexec_buf {struct kimage *image;
@@ -182,8 +187,33 @@ struct kexec_buf {unsigned long buf_min;unsigned long buf_max;bool top_down; +#ifdef CONFIG_CRASH_DUMP +bool random; +#endif }; + +#ifdef CONFIG_CRASH_DUMP +static inline void kexec_random_range_start (unsigned long start, +unsigned long end, +struct kexec_buf *kbuf, +unsigned long *temp_start) +{ +unsigned short i; + +if (kbuf->random) { +get_random_bytes (&i,sizeof (unsigned short )); + *temp_start = start + (end - start) /USHRT_MAX * i; + } +} +#else +static inline void kexec_random_range_start (unsigned long start, +unsigned long end, +struct kexec_buf *kbuf, +unsigned long *temp_start) +{} +#endif +int kexec_load_purgatory (struct kimage *image,struct kexec_buf *kbuf); int kexec_purgatory_get_set_symbol(struct kimage *image, const char *name, void *buf, unsigned int size,
kernel/kexec_file.c +3 -0
@@ -445,6 +445,7 @@ static int locate_mem_hole_top_down(unsigned long start, unsigned long end, temp_end =min (end, kbuf->buf_max); temp_start = temp_end - kbuf->memsz +1 ; +kexec_random_range_start (temp_start, temp_end, kbuf, &temp_start); do { /* align down start */
@@ -483,6 +484,8 @@ static int locate_mem_hole_bottom_up(unsigned long start, unsigned long end, temp_start =max (start, kbuf->buf_min); +kexec_random_range_start (temp_start, end, kbuf, &temp_start); + do { temp_start = ALIGN(temp_start, kbuf->buf_align); temp_end = temp_start + kbuf->memsz - 1;
Signature · 1 line
2.48.1
PATCH v8 2/7 crash_dump: make dm crypt keys persist for the kdump kernel
In reply to Coiby XuA configfs /sys/kernel/config/crash_dm_crypt_keys is provided for user space to make the dm crypt keys persist for the kdump kernel. Take the case of dumping to a LUKS-encrypted target as an example, here is the life cycle of the kdump copies of LUKS volume keys,
1. After the 1st kernel loads the initramfs during boot, systemd uses an user-input passphrase to de-crypt the LUKS volume keys or simply TPM-sealed volume keys and then save the volume keys to specified keyring (using the --link-vk-to-keyring API) and the keys will expire within specified time.
2. A user space tool (kdump initramfs loader like kdump-utils) create key items inside /sys/kernel/config/crash_dm_crypt_keys to inform the 1st kernel which keys are needed.
3. When the kdump initramfs is loaded by the kexec_file_load syscall, the 1st kernel will iterate created key items, save the keys to kdump reserved memory.
4. When the 1st kernel crashes and the kdump initramfs is booted, the kdump initramfs asks the kdump kernel to create a user key using the key stored in kdump reserved memory by writing yes to /sys/kernel/crash_dm_crypt_keys/restore. Then the LUKS encrypted device is unlocked with libcryptsetup's --volume-key-keyring API.
5. The system gets rebooted to the 1st kernel after dumping vmcore to the LUKS encrypted device is finished
Eventually the keys have to stay in the kdump reserved memory for the kdump kernel to unlock encrypted volumes. During this process, some measures like letting the keys expire within specified time are desirable to reduce security risk.
This patch assumes,
1) there are 128 LUKS devices at maximum to be unlocked thus MAX_KEY_NUM=128.
2) a key description won't exceed 128 bytes thus KEY_DESC_MAX_LEN=128.
And here is a demo on how to interact with/sys/kernel/config/crash_dm_crypt_keys,
# Add key #1
mkdir /sys/kernel/config/crash_dm_crypt_keys/7d26b7b4-e342-4d2d-b660-7426b0996720
# Add key #1's description
echo cryptsetup:7d26b7b4-e342-4d2d-b660-7426b0996720 > /sys/kernel/config/crash_dm_crypt_keys/description
# how many keys do we have now?
cat /sys/kernel/config/crash_dm_crypt_keys/count 1
# Add key#2 in the same way
# how many keys do we have now?
cat /sys/kernel/config/crash_dm_crypt_keys/count 2
# the tree structure of /crash_dm_crypt_keys configfs tree /sys/kernel/config/crash_dm_crypt_keys/ /sys/kernel/config/crash_dm_crypt_keys/
├── 7d26b7b4-e342-4d2d-b660-7426b0996720
│ └── description
├── count
├── fce2cd38-4d59-4317-8ce2-1fd24d52c46a
│ └── description
--- Documentation/admin-guide/kdump/kdump.rst | 28 ++++ kernel/Kconfig.kexec | 10 ++ kernel/Makefile | 1 + kernel/crash_dump_dm_crypt.c | 154 ++++++++++++++++++++++ 4 files changed, 193 insertions(+) create mode 100644 kernel/crash_dump_dm_crypt.c
Documentation/admin-guide/kdump/kdump.rst +28 -0
@@ -551,6 +551,34 @@ from within add_taint() whenever the value set in this bitmask matches with the bit flag being set by add_taint(). This will cause a kdump to occur at the add_taint()->panic() call. +Write the dump file to encrypted disk volume +============================================ + +CONFIG_CRASH_DM_CRYPT can be enabled to support saving the dump file to an +encrypted disk volume. User space can interact with +/sys/kernel/config/crash_dm_crypt_keys for setup, + +1. Tell the first kernel what keys are needed to unlock the disk volumes, + # Add key #1 + mkdir /sys/kernel/config/crash_dm_crypt_keys/7d26b7b4-e342-4d2d-b660-7426b0996720 + # Add key #1's description + echo cryptsetup:7d26b7b4-e342-4d2d-b660-7426b0996720 > /sys/kernel/config/crash_dm_crypt_keys/description + + # how many keys do we have now? + cat /sys/kernel/config/crash_dm_crypt_keys/count + 1 + + # Add key #2 in the same way + + # how many keys do we have now? + cat /sys/kernel/config/crash_dm_crypt_keys/count + 2 + +2. Load the dump-capture kernel + +3. After the dump-capture kerne get booted, restore the keys to user keyring + echo yes > /sys/kernel/crash_dm_crypt_keys/restore + Contact =======
kernel/Kconfig.kexec +10 -0
@@ -116,6 +116,16 @@ config CRASH_DUMP For s390, this option also enables zfcpdump. See also <file:Documentation/arch/s390/zfcpdump.rst> +config CRASH_DM_CRYPT + bool "Support saving crash dump to dm-crypt encrypted volume" + depends on KEXEC_FILE + depends on CRASH_DUMP + depends on DM_CRYPT + help + With this option enabled, user space can intereact with + /sys/kernel/config/crash_dm_crypt_keys to make the dm crypt keys + persistent for the dump-capture kernel. + config CRASH_HOTPLUG bool "Update the crash elfcorehdr on system configuration changes" default y
kernel/Makefile +1 -0
@@ -72,6 +72,7 @@ obj-$(CONFIG_VMCORE_INFO) += vmcore_info.o elfcorehdr.o obj-$(CONFIG_CRASH_RESERVE) += crash_reserve.o obj-$(CONFIG_KEXEC_CORE) += kexec_core.o obj-$(CONFIG_CRASH_DUMP) += crash_core.o +obj-$(CONFIG_CRASH_DM_CRYPT) += crash_dump_dm_crypt.o obj-$(CONFIG_KEXEC) += kexec.o obj-$(CONFIG_KEXEC_FILE) += kexec_file.o obj-$(CONFIG_KEXEC_ELF) += kexec_elf.o
kernel/crash_dump_dm_crypt.c new file +154 -0
154 lines not on this page · raw message
Signature · 1 line
2.48.1
Re: [PATCH v8 2/7] crash_dump: make dm crypt keys persist for the kdump kernel
kernel/Kconfig.kexec config CRASH_DUMP · line 128
Quoted 10 lines · Coiby Xu
kernel/Kconfig.kexec +10
-0+config CRASH_DM_CRYPT + bool "Support saving crash dump to dm-crypt encrypted volume" + depends on KEXEC_FILE + depends on CRASH_DUMP + depends on DM_CRYPT + help + With this option enabled, user space can intereact with + /sys/kernel/config/crash_dm_crypt_keys to make the dm crypt keys + persistent for the dump-capture kernel. +
Maybe also add CONFIG_CONFIGFS_FS option? Without it this series code doesn't compile:
Last build lines:
GEN modules.builtin
MODPOST vmlinux.symvers
UPD include/generated/utsversion.h CC init/version-timestamp.o KSYMS .tmp_vmlinux0.kallsyms.S AS .tmp_vmlinux0.kallsyms.o LD .tmp_vmlinux1
ld: vmlinux.o: in function `config_keys_make_item':
/usr/src/linux/kernel/crash_dump_dm_crypt.c:250:(.text+0x228028): undefined reference to `config_item_init_type_name'
ld: vmlinux.o: in function `configfs_dmcrypt_keys_init':
/usr/src/linux/kernel/crash_dump_dm_crypt.c:442:(.init.text+0x71e5c): undefined reference to `config_group_init'
ld: /usr/src/linux/kernel/crash_dump_dm_crypt.c:444:(.init.text+0x71e82): undefined reference to `configfs_register_subsystem'
ld: /usr/src/linux/kernel/crash_dump_dm_crypt.c:454:(.init.text+0x71ef7): undefined reference to `configfs_unregister_subsystem' make[2]: *** [scripts/Makefile.vmlinux:77: vmlinux] Error 1
make[1]: *** [/usr/src/linux/Makefile:1226: vmlinux] Error 2
make: *** [Makefile:251: __sub-make] Error 2
Re: [PATCH v8 2/7] crash_dump: make dm crypt keys persist for the kdump kernel
Quoted 13 lines · Arnaud Lefebvre
kernel/Kconfig.kexec config CRASH_DUMP · line 128
Quoted 10 lines · Coiby Xu
kernel/Kconfig.kexec +10
-0+config CRASH_DM_CRYPT + bool "Support saving crash dump to dm-crypt encrypted volume" + depends on KEXEC_FILE + depends on CRASH_DUMP + depends on DM_CRYPT + help + With this option enabled, user space can intereact with + /sys/kernel/config/crash_dm_crypt_keys to make the dm crypt keys + persistent for the dump-capture kernel. +Maybe also add
CONFIG_CONFIGFS_FSoption? Without it this series code doesn't compile:
I'll add the dependency on CONFIG_CONFIGFS_FS, thanks for your suggestion!
Quoted 19 lines
Last build lines:
GEN modules.builtin
MODPOST vmlinux.symversUPD include/generated/utsversion.h CC init/version-timestamp.o KSYMS .tmp_vmlinux0.kallsyms.S AS .tmp_vmlinux0.kallsyms.o LD .tmp_vmlinux1ld: vmlinux.o: in function `config_keys_make_item':
/usr/src/linux/kernel/crash_dump_dm_crypt.c:250:(.text+0x228028): undefined reference to `config_item_init_type_name'
ld: vmlinux.o: in function `configfs_dmcrypt_keys_init':
/usr/src/linux/kernel/crash_dump_dm_crypt.c:442:(.init.text+0x71e5c): undefined reference to `config_group_init'
ld: /usr/src/linux/kernel/crash_dump_dm_crypt.c:444:(.init.text+0x71e82): undefined reference to `configfs_register_subsystem'
ld: /usr/src/linux/kernel/crash_dump_dm_crypt.c:454:(.init.text+0x71ef7): undefined reference to `configfs_unregister_subsystem' make[2]: *** [scripts/Makefile.vmlinux:77: vmlinux] Error 1
make[1]: *** [/usr/src/linux/Makefile:1226: vmlinux] Error 2
make: *** [Makefile:251: __sub-make] Error 2
Signature · 2 lines
Best regards, Coiby
PATCH v8 3/7 crash_dump: store dm crypt keys in kdump reserved memory
In reply to Coiby XuWhen the kdump kernel image and initrd are loaded, the dm crypts keys will be read from keyring and then stored in kdump reserved memory.
Assume a key won't exceed 256 bytes thus MAX_KEY_SIZE=256 according to "cryptsetup benchmark".
--- include/linux/crash_core.h | 6 +- include/linux/kexec.h | 4 ++ kernel/crash_dump_dm_crypt.c | 128 +++++++++++++++++++++++++++++++++++ 3 files changed, 137 insertions(+), 1 deletion(-)
include/linux/crash_core.h +5 -1
@@ -34,7 +34,11 @@ static inline void arch_kexec_protect_crashkres(void) { }static inline void arch_kexec_unprotect_crashkres (void ) { }#endif - +#ifdef CONFIG_CRASH_DM_CRYPT +int crash_load_dm_crypt_keys (struct kimage *image); +#else +static inline int crash_load_dm_crypt_keys (struct kimage *image) {return 0 ; } +#endif #ifndef arch_crash_handle_hotplug_eventstatic inline void arch_crash_handle_hotplug_event (struct kimage *image,void *arg) { }
include/linux/kexec.h +4 -0
@@ -398,6 +398,10 @@ struct kimage {void *elf_headers;unsigned long elf_headers_sz;unsigned long elf_load_addr; + +/* dm crypt keys buffer */ +unsigned long dm_crypt_keys_addr; +unsigned long dm_crypt_keys_sz; };/* kexec interface functions */
kernel/crash_dump_dm_crypt.c +128 -0
148 lines not on this page · raw message
Signature · 1 line
2.48.1
PATCH v8 4/7 crash_dump: reuse saved dm crypt keys for CPU/memory hot-plugging
In reply to Coiby XuWhen there are CPU and memory hot un/plugs, the dm crypt keys may need to be reloaded again depending on the solution for crash hotplug support. Currently, there are two solutions. One is to utilizes udev to instruct user space to reload the kdump kernel image and initrd, elfcorehdr and etc again. The other is to only update the elfcorehdr segment introduced in commit 247262756121 ("crash:
add generic infrastructure for crash hotplug support").
For the 1st solution, the dm crypt keys need to be reloaded again. The user space can write true to /sys/kernel/config/crash_dm_crypt_key/reuse so the stored keys can be re-used.
For the 2nd solution, the dm crypt keys don't need to be reloaded. Currently, only x86 supports the 2nd solution. If the 2nd solution gets extended to all arches, this patch can be dropped.
--- Documentation/admin-guide/kdump/kdump.rst | 4 ++ kernel/crash_dump_dm_crypt.c | 52 +++++++++++++++++++++-- 2 files changed, 52 insertions(+), 4 deletions(-)
Documentation/admin-guide/kdump/kdump.rst +4 -0
@@ -574,6 +574,10 @@ encrypted disk volume. User space can interact with cat /sys/kernel/config/crash_dm_crypt_keys/count 2 + # To support CPU/memory hot-plugging, re-use keys already saved to reserved + # memory + echo true > /sys/kernel/config/crash_dm_crypt_key/reuse + 2. Load the dump-capture kernel 3. After the dump-capture kerne get booted, restore the keys to user keyring
kernel/crash_dump_dm_crypt.c +48 -4
72 lines not on this page · raw message
Signature · 1 line
2.48.1
PATCH v8 5/7 crash_dump: retrieve dm crypt keys in kdump kernel
In reply to Coiby XuCrash kernel will retrieve the dm crypt keys based on the dmcryptkeys command line parameter. When user space writes the key description to /sys/kernel/config/crash_dm_crypt_key/restore, the crash kernel will save the encryption keys to the user keyring. Then user space e.g. cryptsetup's --volume-key-keyring API can use it to unlock the encrypted device.
--- include/linux/crash_core.h | 1 + include/linux/crash_dump.h | 2 + kernel/crash_dump_dm_crypt.c | 133 +++++++++++++++++++++++++++++++++++ 3 files changed, 136 insertions(+)
include/linux/crash_core.h +1 -0
@@ -36,6 +36,7 @@ static inline void arch_kexec_unprotect_crashkres(void) { }#ifdef CONFIG_CRASH_DM_CRYPT int crash_load_dm_crypt_keys (struct kimage *image); +ssize_t dm_crypt_keys_read (char *buf,size_t count,u64 *ppos);#else static inline int crash_load_dm_crypt_keys (struct kimage *image) {return 0 ; }#endif
include/linux/crash_dump.h +2 -0
@@ -15,6 +15,8 @@extern unsigned long long elfcorehdr_addr;extern unsigned long long elfcorehdr_size; +extern unsigned long long dm_crypt_keys_addr; +#ifdef CONFIG_CRASH_DUMP extern int elfcorehdr_alloc (unsigned long long *addr,unsigned long long *size);extern void elfcorehdr_free (unsigned long long addr);
kernel/crash_dump_dm_crypt.c +133 -0
163 lines not on this page · raw message
Signature · 1 line
2.48.1
PATCH v8 6/7 x86/crash: pass dm crypt keys to kdump kernel
In reply to Coiby Xu1st kernel will build up the kernel command parameter dmcryptkeys as similar to elfcorehdr to pass the memory address of the stored info of dm crypt key to kdump kernel.
--- Documentation/admin-guide/kdump/kdump.rst | 4 ++-- arch/x86/kernel/crash.c | 26 +++++++++++++++++++++-- arch/x86/kernel/kexec-bzimage64.c | 11 ++++++++++ 3 files changed, 37 insertions(+), 4 deletions(-)
Documentation/admin-guide/kdump/kdump.rst +2 -2
@@ -555,8 +555,8 @@ Write the dump file to encrypted disk volume ============================================ CONFIG_CRASH_DM_CRYPT can be enabled to support saving the dump file to an -encrypted disk volume. User space can interact with -/sys/kernel/config/crash_dm_crypt_keys for setup, +encrypted disk volume (only x86_64 supported for now). User space can interact +with /sys/kernel/config/crash_dm_crypt_keys for setup, 1. Tell the first kernel what keys are needed to unlock the disk volumes, # Add key #1
arch/x86/kernel/crash.c +24 -2
@@ -278,6 +278,7 @@ static int memmap_exclude_ranges(struct kimage *image, struct crash_mem *cmem, unsigned long long mend) {unsigned long start, end; +int ret; cmem->ranges[0 ].start = mstart; cmem->ranges[0 ].end = mend;
@@ -286,22 +287,43 @@ static int memmap_exclude_ranges(struct kimage *image, struct crash_mem *cmem,/* Exclude elf header region */ start = image->elf_load_addr; end = start + image->elf_headers_sz -1 ; -return crash_exclude_mem_range (cmem, start, end); + ret =crash_exclude_mem_range (cmem, start, end); + +if (ret) +return ret; + +/* Exclude dm crypt keys region */ +if (image->dm_crypt_keys_addr) { + start = image->dm_crypt_keys_addr; + end = start + image->dm_crypt_keys_sz -1 ; +return crash_exclude_mem_range (cmem, start, end); + } + +return ret; }/* Prepare memory map for crash dump kernel */ int crash_setup_memmap_entries (struct kimage *image,struct boot_params *params) { +unsigned int nr_ranges =0 ;int i, ret =0 ;unsigned long flags;struct e820_entry ei;struct crash_memmap_data cmd;struct crash_mem *cmem; - cmem =vzalloc (struct_size (cmem, ranges,1 )); +/* +* Using random kexec_buf for passing dm crypt keys may cause a range +* split. So use two slots here. +*/ + nr_ranges =2 ; + cmem =vzalloc (struct_size (cmem, ranges, nr_ranges));if (!cmem)return -ENOMEM ; + cmem->max_nr_ranges = nr_ranges; + cmem->nr_ranges =0 ; +memset (&cmd,0 ,sizeof (struct crash_memmap_data )); cmd.params = params;
arch/x86/kernel/kexec-bzimage64.c +11 -0
@@ -76,6 +76,10 @@ static int setup_cmdline(struct kimage *image, struct boot_params *params,if (image->type ==KEXEC_TYPE_CRASH ) { len =sprintf (cmdline_ptr,"elfcorehdr=0x%lx " , image->elf_load_addr); + +if (image->dm_crypt_keys_addr !=0 ) + len +=sprintf (cmdline_ptr + len, +"dmcryptkeys=0x%lx " , image->dm_crypt_keys_addr); }memcpy (cmdline_ptr + len, cmdline, cmdline_len); cmdline_len += len;
@@ -441,6 +445,13 @@ static void *bzImage64_load(struct kimage *image, char *kernel, ret =crash_load_segments (image);if (ret)return ERR_PTR (ret); + ret =crash_load_dm_crypt_keys (image); +if (ret == -ENOENT ) { +kexec_dprintk ("No dm crypt key to load\n" ); + }else if (ret) { +pr_err ("Failed to load dm crypt keys\n" ); +return ERR_PTR (ret); + } }#endif
Signature · 1 line
2.48.1
Re: [PATCH v8 6/7] x86/crash: pass dm crypt keys to kdump kernel
Quoted 5 lines
arch/x86/kernel/kexec-bzimage64.c +0
-0
arch/x86/kernel/kexec-bzimage64.c static int setup_cmdline(struct kimage *image, struct boot_params *params, · line 85
Quoted 10 lines
arch/x86/kernel/kexec-bzimage64.c +4
-0@@ -76,6 +76,10 @@ static int setup_cmdline(struct kimage *image, struct boot_params *params,if (image->type ==KEXEC_TYPE_CRASH ) { len =sprintf (cmdline_ptr,"elfcorehdr=0x%lx " , image->elf_load_addr); + +if (image->dm_crypt_keys_addr !=0 ) + len +=sprintf (cmdline_ptr + len, +"dmcryptkeys=0x%lx " , image->dm_crypt_keys_addr); }memcpy (cmdline_ptr + len, cmdline, cmdline_len); cmdline_len += len;
You are adding another kernel parameter but I believe without taking its length into account. See the MAX_ELFCOREHDR_STR_LEN constant which is added to the params_cmdline_sz variable for the elfcorehdr= parameter.
This will (at least during my tests) truncate the cmdline given to the crash kernel because the next section (efi_map_offset) will have an offset starting inside the cmdline section and it might overwrite the end of it:
kexec-bzimage64.c:480:params_cmdline_sz = sizeof(struct boot_params) + cmdline_len +
MAX_ELFCOREHDR_STR_LEN; <<< Should have + 31 here for "dmcryptkeys=0x<ptr> "
params_cmdline_sz = ALIGN(params_cmdline_sz, 16); kbuf.bufsz = params_cmdline_sz + ALIGN(efi_map_sz, 16) +
sizeof(struct setup_data) + sizeof(struct efi_setup_data) + sizeof(struct setup_data) + RNG_SEED_LENGTH;
And I believe the buffer might be too small.
Also, there is another check a few lines above that needs to take the size into account:
/*
* In case of crash dump, we will append elfcorehdr=<addr> to
* command line. Make sure it does not overflow
*/
if (cmdline_len + MAX_ELFCOREHDR_STR_LEN > header->cmdline_size) {
pr_err("Appending elfcorehdr=<addr> to command line exceeds maximum allowed length\n");
return ERR_PTR(-EINVAL);
}Re: [PATCH v8 6/7] x86/crash: pass dm crypt keys to kdump kernel
Quoted 4 lines · Arnaud Lefebvre
Quoted 4 lines
arch/x86/kernel/kexec-bzimage64.c +0
-0
Quoted 8 lines
arch/x86/kernel/kexec-bzimage64.c static int setup_cmdline(struct kimage *image, struct boot_params *params, · line 82
Quoted 8 lines
arch/x86/kernel/kexec-bzimage64.c +4
-0@@ -76,6 +76,10 @@ static int setup_cmdline(struct kimage *image, struct boot_params *params,if (image->type ==KEXEC_TYPE_CRASH ) { len =sprintf (cmdline_ptr,"elfcorehdr=0x%lx " , image->elf_load_addr); + +if (image->dm_crypt_keys_addr !=0 ) + len +=sprintf (cmdline_ptr + len, +"dmcryptkeys=0x%lx " , image->dm_crypt_keys_addr);
sprintf will return the length of dmcryptkey=xxx which will be added to len.
Quoted 3 lines
arch/x86/kernel/kexec-bzimage64.c static int setup_cmdline(struct kimage *image, struct boot_params *params, · line 85
Quoted 3 lines
arch/x86/kernel/kexec-bzimage64.c +0
-0}memcpy (cmdline_ptr + len, cmdline, cmdline_len); cmdline_len += len;
Then cmdline_len will included the new len.
Quoted 4 lines
You are adding another kernel parameter but I believe without taking its length into account. See the
MAX_ELFCOREHDR_STR_LENconstant which is added to theparams_cmdline_szvariable for the elfcorehdr= parameter.
Thanks for raising the concern! I believe this issue has already been took care of. Please check the above two inline comments:)
Quoted 28 lines
This will (at least during my tests) truncate the cmdline given to the crash kernel because the next section (
efi_map_offset) will have an offset starting inside the cmdline section and it might overwrite the end of it:kexec-bzimage64.c:480:
params_cmdline_sz=sizeof(struct boot_params)+cmdline_len+MAX_ELFCOREHDR_STR_LEN; <<< Should have + 31 here for "dmcryptkeys=0x<ptr> "
params_cmdline_sz=ALIGN(params_cmdline_sz, 16); kbuf.bufsz =params_cmdline_sz+ALIGN(efi_map_sz, 16)+
sizeof(struct setup_data)+sizeof(struct efi_setup_data)+sizeof(struct setup_data)+RNG_SEED_LENGTH;And I believe the buffer might be too small.
Also, there is another check a few lines above that needs to take the size into account:
/*
* In case of crash dump, we will append elfcorehdr=<addr> to
* command line. Make sure it does not overflow
*/if (cmdline_len + MAX_ELFCOREHDR_STR_LEN > header->cmdline_size) { pr_err("Appending elfcorehdr=<addr> to command line exceeds maximum allowed length\n"); return ERR_PTR(-EINVAL); }
Signature · 2 lines
Best regards, Coiby
Re: [PATCH v8 6/7] x86/crash: pass dm crypt keys to kdump kernel
Quoted 17 lines · Coiby Xu
Quoted 4 lines · Arnaud Lefebvre
Quoted 4 lines
arch/x86/kernel/kexec-bzimage64.c +0
-0Quoted 8 lines
arch/x86/kernel/kexec-bzimage64.c static int setup_cmdline(struct kimage *image, struct boot_params *params, · line 82
Quoted 8 lines
arch/x86/kernel/kexec-bzimage64.c +4
-0@@ -76,6 +76,10 @@ static int setup_cmdline(struct kimage *image, struct boot_params *params,if (image->type ==KEXEC_TYPE_CRASH ) { len =sprintf (cmdline_ptr,"elfcorehdr=0x%lx " , image->elf_load_addr); + +if (image->dm_crypt_keys_addr !=0 ) + len +=sprintf (cmdline_ptr + len, +"dmcryptkeys=0x%lx " , image->dm_crypt_keys_addr);sprintf will return the length of dmcryptkey=xxx which will be added to len.
Quoted 5 lines
Quoted 3 lines
arch/x86/kernel/kexec-bzimage64.c static int setup_cmdline(struct kimage *image, struct boot_params *params, · line 85
Quoted 3 lines
arch/x86/kernel/kexec-bzimage64.c +0
-0}memcpy (cmdline_ptr + len, cmdline, cmdline_len); cmdline_len += len;Then
cmdline_lenwill included the new len.
Yes, the cmdline_len is correct. No issue there.
Quoted 9 lines
Quoted 5 lines
You are adding another kernel parameter but I believe without taking its length into account. See the
MAX_ELFCOREHDR_STR_LENconstant which is added to theparams_cmdline_szvariable for the elfcorehdr= parameter.Thanks for raising the concern! I believe this issue has already been took care of. Please check the above two inline comments:)
I'm sorry but I don't think it is. If you look at my comments below:
Quoted 20 lines
Quoted 20 lines
This will (at least during my tests) truncate the cmdline given to the crash kernel because the next section (
efi_map_offset) will have an offset starting inside the cmdline section and it might overwrite the end of it:kexec-bzimage64.c:480:
params_cmdline_sz=sizeof(struct boot_params)+cmdline_len+MAX_ELFCOREHDR_STR_LEN; <<< Should have + 31 here for "dmcryptkeys=0x<ptr> "
params_cmdline_sz=ALIGN(params_cmdline_sz, 16); kbuf.bufsz =params_cmdline_sz+ALIGN(efi_map_sz, 16)+
sizeof(struct setup_data)+sizeof(struct efi_setup_data)+sizeof(struct setup_data)+RNG_SEED_LENGTH;And I believe the buffer might be too small.
Also, there is another check a few lines above that needs to take the size into account:
Quoted 10 lines
Quoted 9 lines
/*
* In case of crash dump, we will append elfcorehdr=<addr> to
* command line. Make sure it does not overflow
*/if (cmdline_len + MAX_ELFCOREHDR_STR_LEN > header->cmdline_size) { pr_err("Appending elfcorehdr=<addr> to command line exceeds maximum allowed length\n"); return ERR_PTR(-EINVAL); }
To try to explain a bit more, we pass a lot of arguments to the crash kernel so the initrd (dracut) can mount the encrypted disk. When I run kexec using the following:
/usr/host/bin/kexec --debug --load-panic /linux-hv '--append=maxcpus=1 reset_devices rd.info rd.cc.kdump root=UUID=d039277c-2ee 3-466a-85eb-db9524398135 console=ttyS0 rd.timeout=10 rd.shell=1 rd.cc.kdump.encrypted rd.cc.kdump.device=UUID=908234b1-c1f3-4150-bfdf-c260907a2447 rd.cc.kdump.keyring=cryptsetup:908234b1-c1f3-4150-bfdf-c260907a2447' --initrd /crash-initrd
kexec debug print those logs:
<snip>
[ 53.642483] kexec-bzImage64: Loaded purgatory at 0xb6ffb000 [ 53.642828] kexec-bzImage64: Loaded boot_param, command line and misc at 0xb6ff9000 bufsz=0x12f0 memsz=0x2000 [ 53.643366] kexec-bzImage64: Loaded 64bit kernel at 0xb1000000 bufsz=0x16a5000 memsz=0x550d000 [ 53.643918] kexec-bzImage64: Loaded initrd at 0xaeb90000 bufsz=0x246f2a1 memsz=0x246f2a1 [ 53.644363] kexec-bzImage64: Final command line is: elfcorehdr=0x77000000
dmcryptkeys=0xa81fc000 maxcpus=1 reset_devices rd.info rd.cc.kdump root=UUID=d039277c-2ee3-466a-85eb-db9524398135 console=ttyS0 rd.timeout=10 rd.shell=1 rd.cc.kdump.encrypted rd.cc.kdump.device=UUID=908234b1-c1f3-4150-bfdf-c260907a2447 rd.cc.kdump.keyring=cryptsetup:908234b1-c1f3-4150-bfdf-c260907a2447 <snip>
Here, we see the full command line, as expected. But when I trigger a panic using echo c > /proc/sysrq-trigger, the first two lines of the crash kernel loading are:
[ 0.000000] Linux version 6.12.23+ (arnaud@exherbo) (gcc (GCC) 12.3.0, GNU ld (GNU Binutils) 2.44) #4 SMP Wed Apr 30 16:11:39 CEST 2025 [ 0.000000] Command line: elfcorehdr=0x77000000 dmcryptkeys=0x9ec14000
maxcpus=1 reset_devices rd.info rd.cc.kdump root=UUID=d039277c-2ee3-466a-85eb-db9524398135 console=ttyS0 rd.timeout=10 rd.shell=1 rd.cc.kdump.encrypted rd.cc.kdump.device=UUID=908234b1-c1f3-4150-bfdf-c260907a2447 rd.cc.kdump.keyring=cryptsetup:908234b1-c1f3-4150-bfdf-c26090
You can see some of it is truncated at the end. It's missing 7a2447. This is because I guess it gets overridden.
My comment above explains where and why it might happen. If I add the size of the dmcryptkeys string length to the params_cmdline_sz variable, we should allocate enough space to have it all. With the patch below, it works fine and I get the full cmdline when my crash kernel boots:
[ 0.000000] Linux version 6.12.23+ (arnaud@exherbo) (gcc (GCC) 12.3.0, GNU ld (GNU Binutils) 2.44) #3 SMP Thu Apr 24 16:42:18 CEST 2025 [ 0.000000] Command line: elfcorehdr=0x77000000 dmcryptkeys=0xa81fc000
maxcpus=1 reset_devices rd.info rd.cc.kdump root=UUID=d039277c-2ee3-466a-85eb-db9524398135 console=ttyS0 rd.timeout=10 rd.shell=1 rd.cc.kdump.encrypted rd.cc.kdump.device=UUID=908234b1-c1f3-4150-bfdf-c260907a2447 rd.cc.kdump.keyring=cryptsetup:908234b1-c1f3-4150-bfdf-c260907a2447
arch/x86/kernel/kexec-bzimage64.c +3 -2
@@ -27,6 +27,7 @@#include <asm/kexec-bzimage64.h> #define MAX_ELFCOREHDR_STR_LEN 30/* elfcorehdr=0x<64bit-value> */ +#define MAX_DMCRYPTKEYS_STR_LEN 31/* * Defines lowest physical address for various segments. Not sure where
@@ -434,7 +435,7 @@ static void *bzImage64_load(struct kimage *image, char *kernel,* In case of crash dump, we will append elfcorehdr=<addr> to * command line. Make sure it does not overflow */ -if (cmdline_len +MAX_ELFCOREHDR_STR_LEN > header->cmdline_size) { +if (cmdline_len +MAX_ELFCOREHDR_STR_LEN +MAX_DMCRYPTKEYS_STR_LEN > header->cmdline_size) {pr_err ("Appending elfcorehdr=<addr> to command line exceeds maximum allowed length\n" );return ERR_PTR (-EINVAL ); }
@@ -478,7 +479,7 @@ static void *bzImage64_load(struct kimage *image, char *kernel,*/ efi_map_sz =efi_get_runtime_map_size (); params_cmdline_sz =sizeof (struct boot_params ) + cmdline_len + -MAX_ELFCOREHDR_STR_LEN ; +MAX_ELFCOREHDR_STR_LEN +MAX_DMCRYPTKEYS_STR_LEN ; params_cmdline_sz =ALIGN (params_cmdline_sz,16 ); kbuf.bufsz = params_cmdline_sz +ALIGN (efi_map_sz,16 ) + sizeof(struct setup_data) +
Let me know if it makes more sense!
Re: [PATCH v8 6/7] x86/crash: pass dm crypt keys to kdump kernel
Quoted 18 lines · Arnaud Lefebvre
Quoted 17 lines · Coiby Xu
Quoted 4 lines · Arnaud Lefebvre
Quoted 4 lines
arch/x86/kernel/kexec-bzimage64.c +0
-0Quoted 8 lines
arch/x86/kernel/kexec-bzimage64.c static int setup_cmdline(struct kimage *image, struct boot_params *params, · line 82
Quoted 8 lines
arch/x86/kernel/kexec-bzimage64.c +4
-0@@ -76,6 +76,10 @@ static int setup_cmdline(struct kimage *image, struct boot_params *params,if (image->type ==KEXEC_TYPE_CRASH ) { len =sprintf (cmdline_ptr,"elfcorehdr=0x%lx " , image->elf_load_addr); + +if (image->dm_crypt_keys_addr !=0 ) + len +=sprintf (cmdline_ptr + len, +"dmcryptkeys=0x%lx " , image->dm_crypt_keys_addr);sprintf will return the length of dmcryptkey=xxx which will be added to len.
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
arch/x86/kernel/kexec-bzimage64.c static int setup_cmdline(struct kimage *image, struct boot_params *params, · line 85
Quoted 3 lines
arch/x86/kernel/kexec-bzimage64.c +0
-0}memcpy (cmdline_ptr + len, cmdline, cmdline_len); cmdline_len += len;Then
cmdline_lenwill included the new len.Yes, the
cmdline_lenis correct. No issue there.
Thanks for confirming it!
Quoted 135 lines
Quoted 10 lines
Quoted 6 lines
You are adding another kernel parameter but I believe without taking its length into account. See the
MAX_ELFCOREHDR_STR_LENconstant which is added to theparams_cmdline_szvariable for the elfcorehdr= parameter.Thanks for raising the concern! I believe this issue has already been took care of. Please check the above two inline comments:)
I'm sorry but I don't think it is. If you look at my comments below:
Quoted 20 lines
Quoted 20 lines
This will (at least during my tests) truncate the cmdline given to the crash kernel because the next section (
efi_map_offset) will have an offset starting inside the cmdline section and it might overwrite the end of it:kexec-bzimage64.c:480:
params_cmdline_sz=sizeof(struct boot_params)+cmdline_len+MAX_ELFCOREHDR_STR_LEN; <<< Should have + 31 here for "dmcryptkeys=0x<ptr> "
params_cmdline_sz=ALIGN(params_cmdline_sz, 16); kbuf.bufsz =params_cmdline_sz+ALIGN(efi_map_sz, 16)+
sizeof(struct setup_data)+sizeof(struct efi_setup_data)+sizeof(struct setup_data)+RNG_SEED_LENGTH;And I believe the buffer might be too small.
Also, there is another check a few lines above that needs to take the size into account:
Quoted 10 lines
Quoted 9 lines
/*
* In case of crash dump, we will append elfcorehdr=<addr> to
* command line. Make sure it does not overflow
*/if (cmdline_len + MAX_ELFCOREHDR_STR_LEN > header->cmdline_size) { pr_err("Appending elfcorehdr=<addr> to command line exceeds maximum allowed length\n"); return ERR_PTR(-EINVAL); }To try to explain a bit more, we pass a lot of arguments to the crash kernel so the initrd (dracut) can mount the encrypted disk. When I run kexec using the following:
/usr/host/bin/kexec--debug --load-panic /linux-hv '--append=maxcpus=1reset_devicesrd.info rd.cc.kdump root=UUID=d039277c-2ee 3-466a-85eb-db9524398135 console=ttyS0 rd.timeout=10 rd.shell=1 rd.cc.kdump.encrypted rd.cc.kdump.device=UUID=908234b1-c1f3-4150-bfdf-c260907a2447 rd.cc.kdump.keyring=cryptsetup:908234b1-c1f3-4150-bfdf-c260907a2447' --initrd /crash-initrdkexec debug print those logs:
<snip>
[ 53.642483] kexec-bzImage64: Loaded purgatory at 0xb6ffb000 [ 53.642828] kexec-bzImage64: Loaded boot_param, command line and misc at 0xb6ff9000 bufsz=0x12f0 memsz=0x2000 [ 53.643366] kexec-bzImage64: Loaded 64bit kernel at 0xb1000000 bufsz=0x16a5000 memsz=0x550d000 [ 53.643918] kexec-bzImage64: Loaded initrd at 0xaeb90000 bufsz=0x246f2a1 memsz=0x246f2a1 [ 53.644363] kexec-bzImage64: Final command line is: elfcorehdr=0x77000000dmcryptkeys=0xa81fc000 maxcpus=1
reset_devicesrd.info rd.cc.kdump root=UUID=d039277c-2ee3-466a-85eb-db9524398135 console=ttyS0 rd.timeout=10 rd.shell=1 rd.cc.kdump.encrypted rd.cc.kdump.device=UUID=908234b1-c1f3-4150-bfdf-c260907a2447 rd.cc.kdump.keyring=cryptsetup:908234b1-c1f3-4150-bfdf-c260907a2447 <snip>Here, we see the full command line, as expected. But when I trigger a panic using
echo c > /proc/sysrq-trigger, the first two lines of the crash kernel loading are:[ 0.000000] Linux version 6.12.23+ (arnaud@exherbo) (gcc (GCC) 12.3.0, GNU ld (GNU Binutils) 2.44) #4 SMP Wed Apr 30 16:11:39 CEST 2025 [ 0.000000] Command line: elfcorehdr=0x77000000 dmcryptkeys=0x9ec14000maxcpus=1
reset_devicesrd.info rd.cc.kdump root=UUID=d039277c-2ee3-466a-85eb-db9524398135 console=ttyS0 rd.timeout=10 rd.shell=1 rd.cc.kdump.encrypted rd.cc.kdump.device=UUID=908234b1-c1f3-4150-bfdf-c260907a2447 rd.cc.kdump.keyring=cryptsetup:908234b1-c1f3-4150-bfdf-c26090You can see some of it is truncated at the end. It's missing
7a2447. This is because I guess it gets overridden.My comment above explains where and why it might happen. If I add the size of the dmcryptkeys string length to the
params_cmdline_szvariable, we should allocate enough space to have it all. With the patch below, it works fine and I get the full cmdline when my crash kernel boots:[ 0.000000] Linux version 6.12.23+ (arnaud@exherbo) (gcc (GCC) 12.3.0, GNU ld (GNU Binutils) 2.44) #3 SMP Thu Apr 24 16:42:18 CEST 2025 [ 0.000000] Command line: elfcorehdr=0x77000000 dmcryptkeys=0xa81fc000maxcpus=1
reset_devicesrd.info rd.cc.kdump root=UUID=d039277c-2ee3-466a-85eb-db9524398135 console=ttyS0 rd.timeout=10 rd.shell=1 rd.cc.kdump.encrypted rd.cc.kdump.device=UUID=908234b1-c1f3-4150-bfdf-c260907a2447 rd.cc.kdump.keyring=cryptsetup:908234b1-c1f3-4150-bfdf-c260907a2447arch/x86/kernel/kexec-bzimage64.c +3
-2@@ -27,6 +27,7 @@#include <asm/kexec-bzimage64.h> #define MAX_ELFCOREHDR_STR_LEN 30/* elfcorehdr=0x<64bit-value> */ +#define MAX_DMCRYPTKEYS_STR_LEN 31/* * Defines lowest physical address for various segments. Not sure where @@ -434,7 +435,7 @@ static void *bzImage64_load(struct kimage *image, char *kernel,* In case of crash dump, we will append elfcorehdr=<addr> to * command line. Make sure it does not overflow */ -if (cmdline_len +MAX_ELFCOREHDR_STR_LEN > header->cmdline_size) { +if (cmdline_len +MAX_ELFCOREHDR_STR_LEN +MAX_DMCRYPTKEYS_STR_LEN > header->cmdline_size) {pr_err ("Appending elfcorehdr=<addr> to command line exceeds maximum allowed length\n" );return ERR_PTR (-EINVAL ); }@@ -478,7 +479,7 @@ static void *bzImage64_load(struct kimage *image, char *kernel,*/ efi_map_sz =efi_get_runtime_map_size (); params_cmdline_sz =sizeof (struct boot_params ) + cmdline_len + -MAX_ELFCOREHDR_STR_LEN ; +MAX_ELFCOREHDR_STR_LEN +MAX_DMCRYPTKEYS_STR_LEN ; params_cmdline_sz =ALIGN (params_cmdline_sz,16 ); kbuf.bufsz = params_cmdline_sz +ALIGN (efi_map_sz,16 ) + sizeof(struct setup_data) +
Quoted 1 line
Let me know if it makes more sense!
Yes, thanks for providing a crystal clear explanation and also a fix! I appreciate your elaboration to show me what the problem is! I'll fix it in v9.
Signature · 2 lines
Best regards, Coiby
PATCH v8 7/7 x86/crash: make the page that stores the dm crypt keys inaccessible
In reply to Coiby XuThis adds an addition layer of protection for the saved copy of dm crypt key. Trying to access the saved copy will cause page fault.
--- arch/x86/kernel/machine_kexec_64.c | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+)
arch/x86/kernel/machine_kexec_64.c +22 -0
@@ -598,13 +598,35 @@ static void kexec_mark_crashkres(bool protect) kexec_mark_range(control, crashk_res.end, protect); } +/* make the memory storing dm crypt keys in/accessible */ +static void kexec_mark_dm_crypt_keys (bool protect) +{ +unsigned long start_paddr, end_paddr; +unsigned int nr_pages; + +if (kexec_crash_image->dm_crypt_keys_addr) { + start_paddr = kexec_crash_image->dm_crypt_keys_addr; + end_paddr = start_paddr + kexec_crash_image->dm_crypt_keys_sz -1 ; + nr_pages = (PAGE_ALIGN (end_paddr) -PAGE_ALIGN_DOWN (start_paddr))/PAGE_SIZE ; +if (protect) +set_memory_np ((unsigned long )phys_to_virt (start_paddr), nr_pages); +else +__set_memory_prot ( + (unsigned long )phys_to_virt (start_paddr), + nr_pages, +__pgprot (_PAGE_PRESENT | _PAGE_NX | _PAGE_RW)); + } +} +void arch_kexec_protect_crashkres (void ) {kexec_mark_crashkres (true); +kexec_mark_dm_crypt_keys (true); }void arch_kexec_unprotect_crashkres (void ) { +kexec_mark_dm_crypt_keys (false);kexec_mark_crashkres (false); }#endif
Signature · 1 line
2.48.1
Quoted 64 lines · Coiby Xu
LUKS is the standard for Linux disk encryption, widely adopted by users, and in some cases, such as Confidential VMs, it is a requirement. With kdump enabled, when the first kernel crashes, the system can boot into the kdump/crash kernel to dump the memory image (i.e.,
/proc/vmcore) to a specified target. However, there are two challenges when dumping vmcore to a LUKS-encrypted device:- Kdump kernel may not be able to decrypt the LUKS partition. For some machines, a system administrator may not have a chance to enter the password to decrypt the device in kdump initramfs after the 1st kernel crashes; For cloud confidential VMs, depending on the policy the kdump kernel may not be able to unseal the keys with TPM and the console virtual keyboard is untrusted.
- LUKS2 by default use the memory-hard Argon2 key derivation function which is quite memory-consuming compared to the limited memory reserved for kdump. Take Fedora example, by default, only 256M is reserved for systems having memory between 4G-64G. With LUKS enabled, ~1300M needs to be reserved for kdump. Note if the memory reserved for kdump can't be used by 1st kernel i.e. an user sees ~1300M memory missing in the 1st kernel.
Besides users (at least for Fedora) usually expect kdump to work out of the box i.e. no manual password input or custom crashkernel value is needed. And it doesn't make sense to derivate the keys again in kdump kernel which seems to be redundant work.
This patch set addresses the above issues by making the LUKS volume keys persistent for kdump kernel with the help of cryptsetup's new APIs (--link-vk-to-keyring/--volume-key-keyring). Here is the life cycle of the kdump copies of LUKS volume keys,
1. After the 1st kernel loads the initramfs during boot, systemd use an user-input passphrase to de-crypt the LUKS volume keys or TPM-sealed key and then save the volume keys to specified keyring (using the --link-vk-to-keyring API) and the key will expire within specified time.
2. A user space tool (kdump initramfs loader like kdump-utils) create key items inside
/sys/kernel/config/crash_dm_crypt_keysto inform the 1st kernel which keys are needed.3. When the kdump initramfs is loaded by the
kexec_file_loadsyscall, the 1st kernel will iterate created key items, save the keys to kdump reserved memory.4. When the 1st kernel crashes and the kdump initramfs is booted, the kdump initramfs asks the kdump kernel to create a user key using the key stored in kdump reserved memory by writing yes to
/sys/kernel/crash_dm_crypt_keys/restore. Then the LUKS encrypted device is unlocked with libcryptsetup's --volume-key-keyring API.5. The system gets rebooted to the 1st kernel after dumping vmcore to the LUKS encrypted device is finished
After libcryptsetup saving the LUKS volume keys to specified keyring, whoever takes this should be responsible for the safety of these copies of keys. The keys will be saved in the memory area exclusively reserved for kdump where even the 1st kernel has no direct access. And further more, two additional protections are added,
- save the copy randomly in kdump reserved memory as suggested by Jan
- clear the_PAGE_PRESENTflag of the page that stores the copy as suggested by Pingfan
Quoted 2 lines
This patch set only supports x86. There will be patches to support other architectures once this patch set gets merged.
This v8 looks good to me, thanks for the great effort, Coiby.
Quoted 65 lines · Baoquan He
Quoted 64 lines · Coiby Xu
LUKS is the standard for Linux disk encryption, widely adopted by users, and in some cases, such as Confidential VMs, it is a requirement. With kdump enabled, when the first kernel crashes, the system can boot into the kdump/crash kernel to dump the memory image (i.e.,
/proc/vmcore) to a specified target. However, there are two challenges when dumping vmcore to a LUKS-encrypted device:- Kdump kernel may not be able to decrypt the LUKS partition. For some machines, a system administrator may not have a chance to enter the password to decrypt the device in kdump initramfs after the 1st kernel crashes; For cloud confidential VMs, depending on the policy the kdump kernel may not be able to unseal the keys with TPM and the console virtual keyboard is untrusted.
- LUKS2 by default use the memory-hard Argon2 key derivation function which is quite memory-consuming compared to the limited memory reserved for kdump. Take Fedora example, by default, only 256M is reserved for systems having memory between 4G-64G. With LUKS enabled, ~1300M needs to be reserved for kdump. Note if the memory reserved for kdump can't be used by 1st kernel i.e. an user sees ~1300M memory missing in the 1st kernel.
Besides users (at least for Fedora) usually expect kdump to work out of the box i.e. no manual password input or custom crashkernel value is needed. And it doesn't make sense to derivate the keys again in kdump kernel which seems to be redundant work.
This patch set addresses the above issues by making the LUKS volume keys persistent for kdump kernel with the help of cryptsetup's new APIs (--link-vk-to-keyring/--volume-key-keyring). Here is the life cycle of the kdump copies of LUKS volume keys,
1. After the 1st kernel loads the initramfs during boot, systemd use an user-input passphrase to de-crypt the LUKS volume keys or TPM-sealed key and then save the volume keys to specified keyring (using the --link-vk-to-keyring API) and the key will expire within specified time.
2. A user space tool (kdump initramfs loader like kdump-utils) create key items inside
/sys/kernel/config/crash_dm_crypt_keysto inform the 1st kernel which keys are needed.3. When the kdump initramfs is loaded by the
kexec_file_loadsyscall, the 1st kernel will iterate created key items, save the keys to kdump reserved memory.4. When the 1st kernel crashes and the kdump initramfs is booted, the kdump initramfs asks the kdump kernel to create a user key using the key stored in kdump reserved memory by writing yes to
/sys/kernel/crash_dm_crypt_keys/restore. Then the LUKS encrypted device is unlocked with libcryptsetup's --volume-key-keyring API.5. The system gets rebooted to the 1st kernel after dumping vmcore to the LUKS encrypted device is finished
After libcryptsetup saving the LUKS volume keys to specified keyring, whoever takes this should be responsible for the safety of these copies of keys. The keys will be saved in the memory area exclusively reserved for kdump where even the 1st kernel has no direct access. And further more, two additional protections are added,
- save the copy randomly in kdump reserved memory as suggested by Jan
- clear the_PAGE_PRESENTflag of the page that stores the copy as suggested by Pingfan
Quoted 6 lines
Quoted 2 lines
This patch set only supports x86. There will be patches to support other architectures once this patch set gets merged.
This v8 looks good to me, thanks for the great effort, Coiby.
Acked-by Baoquan He <[email protected]>
Great, thanks for reviewing and acknowledging the patch set!
Signature · 2 lines
Best regards, Coiby
Hi Andrew,
Quoted 65 lines · Baoquan He
Quoted 64 lines · Coiby Xu
LUKS is the standard for Linux disk encryption, widely adopted by users, and in some cases, such as Confidential VMs, it is a requirement. With kdump enabled, when the first kernel crashes, the system can boot into the kdump/crash kernel to dump the memory image (i.e.,
/proc/vmcore) to a specified target. However, there are two challenges when dumping vmcore to a LUKS-encrypted device:- Kdump kernel may not be able to decrypt the LUKS partition. For some machines, a system administrator may not have a chance to enter the password to decrypt the device in kdump initramfs after the 1st kernel crashes; For cloud confidential VMs, depending on the policy the kdump kernel may not be able to unseal the keys with TPM and the console virtual keyboard is untrusted.
- LUKS2 by default use the memory-hard Argon2 key derivation function which is quite memory-consuming compared to the limited memory reserved for kdump. Take Fedora example, by default, only 256M is reserved for systems having memory between 4G-64G. With LUKS enabled, ~1300M needs to be reserved for kdump. Note if the memory reserved for kdump can't be used by 1st kernel i.e. an user sees ~1300M memory missing in the 1st kernel.
Besides users (at least for Fedora) usually expect kdump to work out of the box i.e. no manual password input or custom crashkernel value is needed. And it doesn't make sense to derivate the keys again in kdump kernel which seems to be redundant work.
This patch set addresses the above issues by making the LUKS volume keys persistent for kdump kernel with the help of cryptsetup's new APIs (--link-vk-to-keyring/--volume-key-keyring). Here is the life cycle of the kdump copies of LUKS volume keys,
1. After the 1st kernel loads the initramfs during boot, systemd use an user-input passphrase to de-crypt the LUKS volume keys or TPM-sealed key and then save the volume keys to specified keyring (using the --link-vk-to-keyring API) and the key will expire within specified time.
2. A user space tool (kdump initramfs loader like kdump-utils) create key items inside
/sys/kernel/config/crash_dm_crypt_keysto inform the 1st kernel which keys are needed.3. When the kdump initramfs is loaded by the
kexec_file_loadsyscall, the 1st kernel will iterate created key items, save the keys to kdump reserved memory.4. When the 1st kernel crashes and the kdump initramfs is booted, the kdump initramfs asks the kdump kernel to create a user key using the key stored in kdump reserved memory by writing yes to
/sys/kernel/crash_dm_crypt_keys/restore. Then the LUKS encrypted device is unlocked with libcryptsetup's --volume-key-keyring API.5. The system gets rebooted to the 1st kernel after dumping vmcore to the LUKS encrypted device is finished
After libcryptsetup saving the LUKS volume keys to specified keyring, whoever takes this should be responsible for the safety of these copies of keys. The keys will be saved in the memory area exclusively reserved for kdump where even the 1st kernel has no direct access. And further more, two additional protections are added,
- save the copy randomly in kdump reserved memory as suggested by Jan
- clear the_PAGE_PRESENTflag of the page that stores the copy as suggested by Pingfan
Quoted 2 lines
Quoted 2 lines
This patch set only supports x86. There will be patches to support other architectures once this patch set gets merged.
Could you pick this patchset into your tree since no conern from other reviewers?
Thanks
Baoquan
Quoted 5 lines
This v8 looks good to me, thanks for the great effort, Coiby.
Acked-by Baoquan He <[email protected]>
Quoted 12 lines · Baoquan He
Hi Andrew,
Quoted 9 lines · Baoquan He
Quoted 8 lines · Coiby Xu
LUKS is the standard for Linux disk encryption, widely adopted by users, and in some cases, such as Confidential VMs, it is a requirement. With kdump enabled, when the first kernel crashes, the system can boot into the kdump/crash kernel to dump the memory image (i.e.,
/proc/vmcore) to a specified target. However, there are two challenges when dumping vmcore to a LUKS-encrypted device:
[...]
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines
This patch set only supports x86. There will be patches to support other architectures once this patch set gets merged.
Could you pick this patchset into your tree since no conern from other reviewers?
Thanks to Baoquan for endorsing the patch set!
Hi Andrew and Dave,
If there is anything further I need to do, any suggestion or feedback will be appreciated!
Or if it's more appropriate for Dave to take the patch set to the x86 tree, it couldn't be better.
Quoted 10 lines
Thanks
BaoquanQuoted 5 lines
This v8 looks good to me, thanks for the great effort, Coiby.
Acked-by Baoquan He <[email protected]>
Signature · 2 lines
Best regards, Coiby
Hi Andrew,
On 02/07/25 at 04:08pm, Coiby Xu wrote:
......snip...
Ping again.
This patchset is adding a generic infrastructure for luks support in crash dumping, and it adds the support in x86 ARCH. Since the x86 related change is only located in kdump only files, won't impact other x86 codes. Could you consider pick this into your tree?
And by the way, this is a kdump only fix, not related to KHO (Kexec HandOver) which David suggested to adapt to earlier. Explained it here to remove misunderstanding.
Thanks
Baoquan
Quoted 19 lines
Documentation/admin-guide/kdump/kdump.rst | 32 ++ arch/x86/kernel/crash.c | 26 +- arch/x86/kernel/kexec-bzimage64.c | 11 + arch/x86/kernel/machine_kexec_64.c | 22 ++ include/linux/crash_core.h | 7 +- include/linux/crash_dump.h | 2 + include/linux/kexec.h | 34 ++ kernel/Kconfig.kexec | 10 + kernel/Makefile | 1 + kernel/crash_dump_dm_crypt.c | 459 ++++++++++++++++++++++ kernel/kexec_file.c | 3 + 11 files changed, 604 insertions(+), 3 deletions(-) create mode 100644 kernel/crash_dump_dm_crypt.cbase-commit:
bb066fe812d6fb3a9d01c073d9f1e2fd5a63403bSignature · 1 line
2.48.1
Hi X86 maintainers, Andrew,
On 02/07/25 at 04:08pm, Coiby Xu wrote:
......snip...
Quoted 2 lines
This patch set only supports x86. There will be patches to support other architectures once this patch set gets merged.
who can help pick this patchset? It has been under many rounds of reviewing, now it's ready for merging from kdump reviewers' side. Or any comments or concern for further work?
Thanks
Baoquan
Quoted 130 lines
v8
- improve documentation [Randy]
- rebase onto 6.14.0-rc1v7
- Baoquan
- differentiate between failing to get dm crypt keys and no dm crypt keys
- add code comments, change function name and etc. to improve code readability
- add documentation for configfs API [Dave]
- fix building error found by kernel test robotv6
- Baoquan
- support AMD SEV
- drop uncessarykeys_header_size
- improve commit message of [PATCH 4/7]- Greg
- switch to configfs
- move ifdef from .c to .h files and reworkkexec_random_start
- use tab instead of space for appended code comment- Process key description in a more flexible way to address problems found by Ondrej
- improve cover letter
- fix an compilation error as found by kernel test robotv5
- Baoquan
- limit the feature of placingkexec_bufrandomly to kdump (CONFIG_CRASH_DUMP)
- add documentation for added sysfs API
- allow to re-send init command to support the case of user switching to a different LUKS-encrypted target
- makeCONFIG_CRASH_DM_CRYPTdepends onCONFIG_DM_CRYPT
- check if the number of keys exceedKEY_NUM_MAX
- rename (struct keys_header).key_count as (struct keys_header).total_keys to improve code readability
- improve commit message
- fix the failure of callingcrash_exclude_mem_range(there is a split ofmem_range)
- use ret instead of r as return code- Greg
- add documentation for added sysfs API
- avoid spamming kernel logs
- fix a buffer overflow issue
- keep the state enums synced up with the string values
- usesysfs_emitother than sprintf
- explainKEY_NUM_MAXandKEY_SIZE_MAX
- s/EXPORT_SYMBOL_GPL/EXPORT_SYMBOL/g
- improve code readability- Rebase onto latest Linus tree
v4
- rebase onto latest Linus tree so Baoquan can apply the patches for code review
- fix kernel test robot warningsv3
- Support CPU/memory hot-plugging [Baoquan]
- Don't save the keys temporarily to simplify the implementation [Baoquan]
- Support multiple LUKS encrypted volumes
- Read logon key instead of user key to improve security [Ondrej]
- A kernel config optionCRASH_DM_CRYPTfor this feature (disabled by default)
- Fix warnings found by kernel test robot
- Rebase the code onto 6.9.0-rc5+v2
- work together with libscryptsetup's --link-vk-to-keyring/--volume-key-keyring APIs [Milan and Ondrej]
- add the case where console virtual keyboard is untrusted for confidential VM
- usedm_crypt_keyinstead of LUKS volume key [Milan and Eric]
- fix some code format issues
- don't move "structkexec_segment" declaration
- Rebase the code onto latest Linus tree (6.7.0)v1
- "Put the luks key handling related tocrash_dumpout into a separate filekernel/crash_dump_luks.c" [Baoquan]
- Put the generic luks handling code before the x86 specific code to make it easier for other arches to follow suit [Baoquan]
- Usephys_to_virtinstead of "pfn -> page -> vaddr" [Dave Hansen]
- Drop the RFC prefix [Dave Young]
- Rebase the code onto latest Linus tree (6.4.0-rc4)RFC v2
- libcryptsetup interacts with the kernel via sysfs instead of "hacking" dm-crypt
- to save a kdump copy of the LUKS volume key in 1st kernel
- to add a logon key using the copy for libcryptsetup in kdump kernel [Milan]
- to avoid the incorrect usage of LUKS master key in dm-crypt [Milan]
- save the kdump copy of LUKS volume key randomly [Jan]
- mark the kdump copy inaccessible [Pingfan]
- Miscellaneous
- explain when operations related to the LUKS volume key happen [Jan]
- s/master key/volume key/g
- usecrash_instead ofkexec_as function prefix
- fix commit subject prefixes e.g. "x86, kdump" to x86/crashCoiby Xu (7):
kexec_file: allow to placekexec_bufrandomly
crash_dump: make dm crypt keys persist for the kdump kernel
crash_dump: store dm crypt keys in kdump reserved memory
crash_dump: reuse saved dm crypt keys for CPU/memory hot-plugging
crash_dump: retrieve dm crypt keys in kdump kernel x86/crash: pass dm crypt keys to kdump kernel
x86/crash: make the page that stores the dm crypt keys inaccessibleDocumentation/admin-guide/kdump/kdump.rst | 32 ++ arch/x86/kernel/crash.c | 26 +- arch/x86/kernel/kexec-bzimage64.c | 11 + arch/x86/kernel/machine_kexec_64.c | 22 ++ include/linux/crash_core.h | 7 +- include/linux/crash_dump.h | 2 + include/linux/kexec.h | 34 ++ kernel/Kconfig.kexec | 10 + kernel/Makefile | 1 + kernel/crash_dump_dm_crypt.c | 459 ++++++++++++++++++++++ kernel/kexec_file.c | 3 + 11 files changed, 604 insertions(+), 3 deletions(-) create mode 100644 kernel/crash_dump_dm_crypt.cbase-commit:
bb066fe812d6fb3a9d01c073d9f1e2fd5a63403bSignature · 1 line
2.48.1
Quoted 64 lines · Coiby Xu
LUKS is the standard for Linux disk encryption, widely adopted by users, and in some cases, such as Confidential VMs, it is a requirement. With kdump enabled, when the first kernel crashes, the system can boot into the kdump/crash kernel to dump the memory image (i.e.,
/proc/vmcore) to a specified target. However, there are two challenges when dumping vmcore to a LUKS-encrypted device:- Kdump kernel may not be able to decrypt the LUKS partition. For some machines, a system administrator may not have a chance to enter the password to decrypt the device in kdump initramfs after the 1st kernel crashes; For cloud confidential VMs, depending on the policy the kdump kernel may not be able to unseal the keys with TPM and the console virtual keyboard is untrusted.
- LUKS2 by default use the memory-hard Argon2 key derivation function which is quite memory-consuming compared to the limited memory reserved for kdump. Take Fedora example, by default, only 256M is reserved for systems having memory between 4G-64G. With LUKS enabled, ~1300M needs to be reserved for kdump. Note if the memory reserved for kdump can't be used by 1st kernel i.e. an user sees ~1300M memory missing in the 1st kernel.
Besides users (at least for Fedora) usually expect kdump to work out of the box i.e. no manual password input or custom crashkernel value is needed. And it doesn't make sense to derivate the keys again in kdump kernel which seems to be redundant work.
This patch set addresses the above issues by making the LUKS volume keys persistent for kdump kernel with the help of cryptsetup's new APIs (--link-vk-to-keyring/--volume-key-keyring). Here is the life cycle of the kdump copies of LUKS volume keys,
1. After the 1st kernel loads the initramfs during boot, systemd use an user-input passphrase to de-crypt the LUKS volume keys or TPM-sealed key and then save the volume keys to specified keyring (using the --link-vk-to-keyring API) and the key will expire within specified time.
2. A user space tool (kdump initramfs loader like kdump-utils) create key items inside
/sys/kernel/config/crash_dm_crypt_keysto inform the 1st kernel which keys are needed.3. When the kdump initramfs is loaded by the
kexec_file_loadsyscall, the 1st kernel will iterate created key items, save the keys to kdump reserved memory.4. When the 1st kernel crashes and the kdump initramfs is booted, the kdump initramfs asks the kdump kernel to create a user key using the key stored in kdump reserved memory by writing yes to
/sys/kernel/crash_dm_crypt_keys/restore. Then the LUKS encrypted device is unlocked with libcryptsetup's --volume-key-keyring API.5. The system gets rebooted to the 1st kernel after dumping vmcore to the LUKS encrypted device is finished
After libcryptsetup saving the LUKS volume keys to specified keyring, whoever takes this should be responsible for the safety of these copies of keys. The keys will be saved in the memory area exclusively reserved for kdump where even the 1st kernel has no direct access. And further more, two additional protections are added,
- save the copy randomly in kdump reserved memory as suggested by Jan
- clear the_PAGE_PRESENTflag of the page that stores the copy as suggested by Pingfan
Quoted 3 lines
This patch set only supports x86. There will be patches to support other architectures once this patch set gets merged.
I'm not sure what's the problem here but I can reliably trigger a kernel panic on a qemu VM + custom kernel (compiled from bb066fe812d6fb3a9d01c073d9f1e2fd5a63403b + your patches).
When I configure the crash configfs and call kexec in a systemd service using ExecStart=, the panic occurs when I start the service:
~ # cat /etc/systemd/system/my-kexec.service [Unit]
Description=kexec loading for the crash capture kernel
[Service]
Type=oneshot
ExecStart=/usr/bin/mkdir /sys/kernel/config/crash_dm_crypt_keys/mykey ExecStart=/usr/bin/echo cryptsetup:mykey >/sys/kernel/config/crash_dm_crypt_keys/mykey/description ExecStart=/usr/host/bin/kexec --debug --load-panic /linux-hv --initrd /crash-initrd KeyringMode=shared
[Install]
WantedBy=default.target
Starting the service:
~ # systemctl start my-kexec.servicekexec_file: kernel: 00000000ace85dcc kernel_size: 0x16e3000crash_core: Crash PT_LOAD ELF header. phdr=00000000d08940fa vaddr=0xffff888000100000, paddr=0x100000, sz=0x700000 e_phnum=11 p_offset=0x100000crash_core: Crash PT_LOAD ELF header. phdr=00000000304ef570 vaddr=0xffff888000808000, paddr=0x808000, sz=0x3000 e_phnum=12 p_offset=0x808000crash_core: Crash PT_LOAD ELF header. phdr=000000000275e248 vaddr=0xffff88800080c000, paddr=0x80c000, sz=0x5000 e_phnum=13 p_offset=0x80c000crash_core: Crash PT_LOAD ELF header. phdr=000000004e47ca09 vaddr=0xffff888000900000, paddr=0x900000, sz=0xa5700000 e_phnum=14 p_offset=0x900000crash_core: Crash PT_LOAD ELF header. phdr=00000000e56c8350 vaddr=0xffff8880b6000000, paddr=0xb6000000, sz=0x7d51018 e_phnum=15 p_offset=0xb6000000crash_core: Crash PT_LOAD ELF header. phdr=0000000099d67ff3 vaddr=0xffff8880bdd51018, paddr=0xbdd51018, sz=0x27440 e_phnum=16 p_offset=0xbdd51018crash_core: Crash PT_LOAD ELF header. phdr=00000000461a2f21 vaddr=0xffff8880bdd78458, paddr=0xbdd78458, sz=0xbc0 e_phnum=17 p_offset=0xbdd78458crash_core: Crash PT_LOAD ELF header. phdr=0000000058149b54 vaddr=0xffff8880bdd79018, paddr=0xbdd79018, sz=0x9a40 e_phnum=18 p_offset=0xbdd79018crash_core: Crash PT_LOAD ELF header. phdr=000000001e30ff2c vaddr=0xffff8880bdd82a58, paddr=0xbdd82a58, sz=0xdbc5a8 e_phnum=19 p_offset=0xbdd82a58crash_core: Crash PT_LOAD ELF header. phdr=00000000e67a9768 vaddr=0xffff8880bec00000, paddr=0xbec00000, sz=0xaed000 e_phnum=20 p_offset=0xbec00000crash_core: Crash PT_LOAD ELF header. phdr=000000005909c4c6 vaddr=0xffff8880bf9ff000, paddr=0xbf9ff000, sz=0x453000 e_phnum=21 p_offset=0xbf9ff000crash_core: Crash PT_LOAD ELF header. phdr=00000000473d74ef vaddr=0xffff8880bfe58000, paddr=0xbfe58000, sz=0x64000 e_phnum=22 p_offset=0xbfe58000crash_core: Crash PT_LOAD ELF header. phdr=00000000abde8123 vaddr=0xffff888100000000, paddr=0x100000000, sz=0x23f000000 e_phnum=23 p_offset=0x100000000crash_core: Crash PT_LOAD ELF header. phdr=00000000bda3e0bf vaddr=0xffff88843f000000, paddr=0x43f000000, sz=0x1000000 e_phnum=24 p_offset=0x43f000000
kexec: Loaded ELF headers at 0x33f000000 bufsz=0x1000 memsz=0xe1000
BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 5 UID: 0 PID: 3812 Comm: kexec Not tainted 6.14.0-rc1+ #20 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 2025.02-6 04/08/2025 RIP: 0010:sized_strscpy+0x71/0x150 Code: b9 80 80 80 80 80 80 80 80 48 c1 e8 03 48 8d 1c c5 08 00 00 00 31 c0 eb 11 48 89 34 07 48 83 c0 08 48 39 d8 0f 84 83 00 00 00 <49> 8b 34 00 4a 8d 14 1e 49 89 f2 49 f7 d2 4c 21 d2 4c 8d 14 07 4c RSP: 0018:ffffc9000420fc68 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000080 RCX: 0000000000000080 RDX: 0000000000000080 RSI: 0000000000000000 RDI: ffff8881030ec808 RBP: ffff888109724000 R08: 0000000000000000 R09: 8080808080808080 R10: ffffc9000420fc78 R11: fefefefefefefeff R12: ffffc90004219000 R13: ffff888104a80000 R14: 0000000000000008 R15: 0000000000000000 FS: 00007f09ea73f740(0000) GS:ffff88843fc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000120760002 CR4: 0000000000772ef0 PKRU: 55555554 Call Trace: <TASK> ? __die+0x23/0x60 ? page_fault_oops+0x177/0x510 ? _prb_read_valid+0x2e7/0x370 ? exc_page_fault+0x6f/0x130 ? asm_exc_page_fault+0x26/0x30 ? sized_strscpy+0x71/0x150 crash_load_dm_crypt_keys+0x1bc/0x370 bzImage64_load+0x41b/0xa30 __do_sys_kexec_file_load+0x2af/0x8a0 do_syscall_64+0x4b/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f09ea848d6d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48
89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6b 70 0d 00 f7 d8 64 89 01 48
RSP: 002b:00007fff8cf979e8 EFLAGS: 00000206 ORIG_RAX: 0000000000000140
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f09ea848d6d
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000003
RBP: 0000000000000003 R08: 000000000000000a R09: 00007fff8cf97a10
R10: 000055de70eee9a0 R11: 0000000000000206 R12: 0000000000000003
R13: 00007fff8cf97d08 R14: 000055de4c336448 R15: 0000000000000004
</TASK> CR2: 0000000000000000 ---[ end trace 0000000000000000 ]--- RIP: 0010:sized_strscpy+0x71/0x150 Code: b9 80 80 80 80 80 80 80 80 48 c1 e8 03 48 8d 1c c5 08 00 00 00 31 c0 eb 11 48 89 34 07 48 83 c0 08 48 39 d8 0f 84 83 00 00 00 <49> 8b 34 00 4a 8d 14 1e 49 89 f2 49 f7 d2 4c 21 d2 4c 8d 14 07 4c RSP: 0018:ffffc9000420fc68 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000080 RCX: 0000000000000080 RDX: 0000000000000080 RSI: 0000000000000000 RDI: ffff8881030ec808 RBP: ffff888109724000 R08: 0000000000000000 R09: 8080808080808080 R10: ffffc9000420fc78 R11: fefefefefefefeff R12: ffffc90004219000 R13: ffff888104a80000 R14: 0000000000000008 R15: 0000000000000000 FS: 00007f09ea73f740(0000) GS:ffff88843fc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000120760002 CR4: 0000000000772ef0 PKRU: 55555554 Kernel panic - not syncing: Fatal exception
Kernel Offset: disabled
Calling a script that does the same thing works fine and loads the keys correctly:
[Service]
ExecStart=/root/kexec.sh
~ # cat /root/kexec.sh
#!/bin/bash
mkdir /sys/kernel/config/crash_dm_crypt_keys/mykey
echo cryptsetup:mykey > /sys/kernel/config/crash_dm_crypt_keys/mykey/description /usr/host/bin/kexec --debug --load-panic /linux-hv --initrd /crash-initrd
If that's any help, my crypttab:
~ # cat /etc/crypttab
root UUID=8001fca4-2e54-48e9-9235-031c19fc6e36 none luks,link-volume-key=@u::%logon:cryptsetup:mykey
If you can't reproduce, I can help track this. Just let me know if you need any help.
Quoted 65 lines · Arnaud Lefebvre
Quoted 64 lines · Coiby Xu
LUKS is the standard for Linux disk encryption, widely adopted by users, and in some cases, such as Confidential VMs, it is a requirement. With kdump enabled, when the first kernel crashes, the system can boot into the kdump/crash kernel to dump the memory image (i.e.,
/proc/vmcore) to a specified target. However, there are two challenges when dumping vmcore to a LUKS-encrypted device:- Kdump kernel may not be able to decrypt the LUKS partition. For some machines, a system administrator may not have a chance to enter the password to decrypt the device in kdump initramfs after the 1st kernel crashes; For cloud confidential VMs, depending on the policy the kdump kernel may not be able to unseal the keys with TPM and the console virtual keyboard is untrusted.
- LUKS2 by default use the memory-hard Argon2 key derivation function which is quite memory-consuming compared to the limited memory reserved for kdump. Take Fedora example, by default, only 256M is reserved for systems having memory between 4G-64G. With LUKS enabled, ~1300M needs to be reserved for kdump. Note if the memory reserved for kdump can't be used by 1st kernel i.e. an user sees ~1300M memory missing in the 1st kernel.
Besides users (at least for Fedora) usually expect kdump to work out of the box i.e. no manual password input or custom crashkernel value is needed. And it doesn't make sense to derivate the keys again in kdump kernel which seems to be redundant work.
This patch set addresses the above issues by making the LUKS volume keys persistent for kdump kernel with the help of cryptsetup's new APIs (--link-vk-to-keyring/--volume-key-keyring). Here is the life cycle of the kdump copies of LUKS volume keys,
1. After the 1st kernel loads the initramfs during boot, systemd use an user-input passphrase to de-crypt the LUKS volume keys or TPM-sealed key and then save the volume keys to specified keyring (using the --link-vk-to-keyring API) and the key will expire within specified time.
2. A user space tool (kdump initramfs loader like kdump-utils) create key items inside
/sys/kernel/config/crash_dm_crypt_keysto inform the 1st kernel which keys are needed.3. When the kdump initramfs is loaded by the
kexec_file_loadsyscall, the 1st kernel will iterate created key items, save the keys to kdump reserved memory.4. When the 1st kernel crashes and the kdump initramfs is booted, the kdump initramfs asks the kdump kernel to create a user key using the key stored in kdump reserved memory by writing yes to
/sys/kernel/crash_dm_crypt_keys/restore. Then the LUKS encrypted device is unlocked with libcryptsetup's --volume-key-keyring API.5. The system gets rebooted to the 1st kernel after dumping vmcore to the LUKS encrypted device is finished
After libcryptsetup saving the LUKS volume keys to specified keyring, whoever takes this should be responsible for the safety of these copies of keys. The keys will be saved in the memory area exclusively reserved for kdump where even the 1st kernel has no direct access. And further more, two additional protections are added,
- save the copy randomly in kdump reserved memory as suggested by Jan
- clear the_PAGE_PRESENTflag of the page that stores the copy as suggested by Pingfan
Quoted 7 lines
Quoted 3 lines
This patch set only supports x86. There will be patches to support other architectures once this patch set gets merged.
I'm not sure what's the problem here but I can reliably trigger a kernel panic on a qemu VM + custom kernel (compiled from
bb066fe812d6fb3a9d01c073d9f1e2fd5a63403b+ your patches).
Hi Arnaud,
Thanks for testing the patches, finding this issue and also sharing the details to reproduce it!
Quoted 8 lines
When I configure the crash configfs and call kexec in a systemd service using ExecStart=, the panic occurs when I start the service:
~ # cat
/etc/systemd/system/my-kexec.service[Unit]
Description=kexec loading for the crash capture kernel
Quoted 6 lines
[Service]
Type=oneshot
ExecStart=/usr/bin/mkdir/sys/kernel/config/crash_dm_crypt_keys/mykeyExecStart=/usr/bin/echo cryptsetup:mykey >/sys/kernel/config/crash_dm_crypt_keys/mykey/description ExecStart=/usr/host/bin/kexec --debug --load-panic /linux-hv --initrd /crash-initrd KeyringMode=shared
Can you try putting the above commands into a script e.g. /usr/local/bin/my-kexec.sh and then using ExecStart=/usr/local/bin/my-kexec.sh
so I can be more sure that I've reproduced your issue?
Quoted 140 lines
[Install]
WantedBy=default.targetStarting the service:
~ # systemctl start my-kexec.service
kexec_file: kernel:00000000ace85dcckernel_size:0x16e3000crash_core: CrashPT_LOADELF header. phdr=00000000d08940fa vaddr=0xffff888000100000, paddr=0x100000, sz=0x700000 e_phnum=11 p_offset=0x100000crash_core: CrashPT_LOADELF header. phdr=00000000304ef570 vaddr=0xffff888000808000, paddr=0x808000, sz=0x3000 e_phnum=12 p_offset=0x808000crash_core: CrashPT_LOADELF header. phdr=000000000275e248 vaddr=0xffff88800080c000, paddr=0x80c000, sz=0x5000 e_phnum=13 p_offset=0x80c000crash_core: CrashPT_LOADELF header. phdr=000000004e47ca09 vaddr=0xffff888000900000, paddr=0x900000, sz=0xa5700000 e_phnum=14 p_offset=0x900000crash_core: CrashPT_LOADELF header. phdr=00000000e56c8350 vaddr=0xffff8880b6000000, paddr=0xb6000000, sz=0x7d51018 e_phnum=15 p_offset=0xb6000000crash_core: CrashPT_LOADELF header. phdr=0000000099d67ff3 vaddr=0xffff8880bdd51018, paddr=0xbdd51018, sz=0x27440 e_phnum=16 p_offset=0xbdd51018crash_core: CrashPT_LOADELF header. phdr=00000000461a2f21 vaddr=0xffff8880bdd78458, paddr=0xbdd78458, sz=0xbc0 e_phnum=17 p_offset=0xbdd78458crash_core: CrashPT_LOADELF header. phdr=0000000058149b54 vaddr=0xffff8880bdd79018, paddr=0xbdd79018, sz=0x9a40 e_phnum=18 p_offset=0xbdd79018crash_core: CrashPT_LOADELF header. phdr=000000001e30ff2c vaddr=0xffff8880bdd82a58, paddr=0xbdd82a58, sz=0xdbc5a8 e_phnum=19 p_offset=0xbdd82a58crash_core: CrashPT_LOADELF header. phdr=00000000e67a9768 vaddr=0xffff8880bec00000, paddr=0xbec00000, sz=0xaed000 e_phnum=20 p_offset=0xbec00000crash_core: CrashPT_LOADELF header. phdr=000000005909c4c6 vaddr=0xffff8880bf9ff000, paddr=0xbf9ff000, sz=0x453000 e_phnum=21 p_offset=0xbf9ff000crash_core: CrashPT_LOADELF header. phdr=00000000473d74ef vaddr=0xffff8880bfe58000, paddr=0xbfe58000, sz=0x64000 e_phnum=22 p_offset=0xbfe58000crash_core: CrashPT_LOADELF header. phdr=00000000abde8123 vaddr=0xffff888100000000, paddr=0x100000000, sz=0x23f000000 e_phnum=23 p_offset=0x100000000crash_core: CrashPT_LOADELF header. phdr=00000000bda3e0bf vaddr=0xffff88843f000000, paddr=0x43f000000, sz=0x1000000 e_phnum=24 p_offset=0x43f000000
kexec: Loaded ELF headers at0x33f000000bufsz=0x1000 memsz=0xe1000BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 5 UID: 0 PID: 3812 Comm: kexec Not tainted 6.14.0-rc1+ #20 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 2025.02-6 04/08/2025 RIP: 0010:sized_strscpy+0x71/0x150 Code: b9 80 80 80 80 80 80 80 80 48 c1 e8 03 48 8d 1c c5 08 00 00 00 31 c0 eb 11 48 89 34 07 48 83 c0 08 48 39 d8 0f 84 83 00 00 00 <49> 8b 34 00 4a 8d 14 1e 49 89 f2 49 f7 d2 4c 21 d2 4c 8d 14 07 4c RSP: 0018:ffffc9000420fc68 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000080 RCX: 0000000000000080 RDX: 0000000000000080 RSI: 0000000000000000 RDI: ffff8881030ec808 RBP: ffff888109724000 R08: 0000000000000000 R09: 8080808080808080 R10: ffffc9000420fc78 R11: fefefefefefefeff R12: ffffc90004219000 R13: ffff888104a80000 R14: 0000000000000008 R15: 0000000000000000 FS: 00007f09ea73f740(0000) GS:ffff88843fc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000120760002 CR4: 0000000000772ef0 PKRU: 55555554 Call Trace: <TASK> ? __die+0x23/0x60 ? page_fault_oops+0x177/0x510 ? _prb_read_valid+0x2e7/0x370 ? exc_page_fault+0x6f/0x130 ? asm_exc_page_fault+0x26/0x30 ? sized_strscpy+0x71/0x150 crash_load_dm_crypt_keys+0x1bc/0x370 bzImage64_load+0x41b/0xa30 __do_sys_kexec_file_load+0x2af/0x8a0 do_syscall_64+0x4b/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f09ea848d6d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 4889 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6b 70 0d 00 f7 d8 64 89 01 48
RSP: 002b:00007fff8cf979e8 EFLAGS: 00000206ORIG_RAX: 0000000000000140
RAX: ffffffffffffffda RBX: 0000000000000000 RCX:00007f09ea848d6d
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000003
RBP: 0000000000000003 R08:000000000000000aR09:00007fff8cf97a10
R10:000055de70eee9a0R11: 0000000000000206 R12: 0000000000000003
R13:00007fff8cf97d08R14:000055de4c336448R15: 0000000000000004</TASK> CR2: 0000000000000000 ---[ end trace 0000000000000000 ]--- RIP: 0010:sized_strscpy+0x71/0x150 Code: b9 80 80 80 80 80 80 80 80 48 c1 e8 03 48 8d 1c c5 08 00 00 00 31 c0 eb 11 48 89 34 07 48 83 c0 08 48 39 d8 0f 84 83 00 00 00 <49> 8b 34 00 4a 8d 14 1e 49 89 f2 49 f7 d2 4c 21 d2 4c 8d 14 07 4c RSP: 0018:ffffc9000420fc68 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000080 RCX: 0000000000000080 RDX: 0000000000000080 RSI: 0000000000000000 RDI: ffff8881030ec808 RBP: ffff888109724000 R08: 0000000000000000 R09: 8080808080808080 R10: ffffc9000420fc78 R11: fefefefefefefeff R12: ffffc90004219000 R13: ffff888104a80000 R14: 0000000000000008 R15: 0000000000000000 FS: 00007f09ea73f740(0000) GS:ffff88843fc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000120760002 CR4: 0000000000772ef0 PKRU: 55555554 Kernel panic - not syncing: Fatal exceptionKernel Offset: disabled
Calling a script that does the same thing works fine and loads the keys correctly:
[Service]
ExecStart=/root/kexec.sh~ # cat
/root/kexec.sh
#!/bin/bashmkdir
/sys/kernel/config/crash_dm_crypt_keys/mykey
echo cryptsetup:mykey >/sys/kernel/config/crash_dm_crypt_keys/mykey/description/usr/host/bin/kexec--debug --load-panic /linux-hv --initrd /crash-initrdIf that's any help, my crypttab:
~ # cat
/etc/crypttab
root UUID=8001fca4-2e54-48e9-9235-031c19fc6e36 none luks,link-volume-key=@u::%logon:cryptsetup:mykeyIf you can't reproduce, I can help track this. Just let me know if you need any help.
Signature · 2 lines
Best regards, Coiby
Quoted 70 lines · Coiby Xu
Quoted 69 lines · Arnaud Lefebvre
Quoted 67 lines · Coiby Xu
LUKS is the standard for Linux disk encryption, widely adopted by users, and in some cases, such as Confidential VMs, it is a requirement. With kdump enabled, when the first kernel crashes, the system can boot into the kdump/crash kernel to dump the memory image (i.e.,
/proc/vmcore) to a specified target. However, there are two challenges when dumping vmcore to a LUKS-encrypted device:- Kdump kernel may not be able to decrypt the LUKS partition. For some machines, a system administrator may not have a chance to enter the password to decrypt the device in kdump initramfs after the 1st kernel crashes; For cloud confidential VMs, depending on the policy the kdump kernel may not be able to unseal the keys with TPM and the console virtual keyboard is untrusted.
- LUKS2 by default use the memory-hard Argon2 key derivation function which is quite memory-consuming compared to the limited memory reserved for kdump. Take Fedora example, by default, only 256M is reserved for systems having memory between 4G-64G. With LUKS enabled, ~1300M needs to be reserved for kdump. Note if the memory reserved for kdump can't be used by 1st kernel i.e. an user sees ~1300M memory missing in the 1st kernel.
Besides users (at least for Fedora) usually expect kdump to work out of the box i.e. no manual password input or custom crashkernel value is needed. And it doesn't make sense to derivate the keys again in kdump kernel which seems to be redundant work.
This patch set addresses the above issues by making the LUKS volume keys persistent for kdump kernel with the help of cryptsetup's new APIs (--link-vk-to-keyring/--volume-key-keyring). Here is the life cycle of the kdump copies of LUKS volume keys,
1. After the 1st kernel loads the initramfs during boot, systemd use an user-input passphrase to de-crypt the LUKS volume keys or TPM-sealed key and then save the volume keys to specified keyring (using the --link-vk-to-keyring API) and the key will expire within specified time.
2. A user space tool (kdump initramfs loader like kdump-utils) create key items inside
/sys/kernel/config/crash_dm_crypt_keysto inform the 1st kernel which keys are needed.3. When the kdump initramfs is loaded by the
kexec_file_loadsyscall, the 1st kernel will iterate created key items, save the keys to kdump reserved memory.4. When the 1st kernel crashes and the kdump initramfs is booted, the kdump initramfs asks the kdump kernel to create a user key using the key stored in kdump reserved memory by writing yes to
/sys/kernel/crash_dm_crypt_keys/restore. Then the LUKS encrypted device is unlocked with libcryptsetup's --volume-key-keyring API.5. The system gets rebooted to the 1st kernel after dumping vmcore to the LUKS encrypted device is finished
After libcryptsetup saving the LUKS volume keys to specified keyring, whoever takes this should be responsible for the safety of these copies of keys. The keys will be saved in the memory area exclusively reserved for kdump where even the 1st kernel has no direct access. And further more, two additional protections are added,
- save the copy randomly in kdump reserved memory as suggested by Jan
- clear the_PAGE_PRESENTflag of the page that stores the copy as suggested by PingfanThis patch set only supports x86. There will be patches to support other architectures once this patch set gets merged.
Quoted 9 lines
Quoted 3 lines
I'm not sure what's the problem here but I can reliably trigger a kernel panic on a qemu VM + custom kernel (compiled from
bb066fe812d6fb3a9d01c073d9f1e2fd5a63403b+ your patches).Hi Arnaud,
Thanks for testing the patches, finding this issue and also sharing the details to reproduce it!
Hello,
You're welcome, thanks to you for this patch series!
Quoted 15 lines
Quoted 8 lines
When I configure the crash configfs and call kexec in a systemd service using ExecStart=, the panic occurs when I start the service:
~ # cat
/etc/systemd/system/my-kexec.service[Unit]
Description=kexec loading for the crash capture kernelQuoted 6 lines
[Service]
Type=oneshot
ExecStart=/usr/bin/mkdir/sys/kernel/config/crash_dm_crypt_keys/mykeyExecStart=/usr/bin/echo cryptsetup:mykey >/sys/kernel/config/crash_dm_crypt_keys/mykey/description ExecStart=/usr/host/bin/kexec --debug --load-panic /linux-hv --initrd /crash-initrd KeyringMode=shared
Quoted 5 lines
Can you try putting the above commands into a script e.g.
/usr/local/bin/my-kexec.shand then using ExecStart=/usr/local/bin/my-kexec.sh
so I can be more sure that I've reproduced your issue?
I believe that's what I wrote at the end of my previous message (see below the panic trace). It works fine using a script like that.
Did you miss it or is there a difference with what you're asking?
Quoted 145 lines
Quoted 140 lines
[Install]
WantedBy=default.targetStarting the service:
~ # systemctl start my-kexec.service
kexec_file: kernel:00000000ace85dcckernel_size:0x16e3000crash_core: CrashPT_LOADELF header. phdr=00000000d08940fa vaddr=0xffff888000100000, paddr=0x100000, sz=0x700000 e_phnum=11 p_offset=0x100000crash_core: CrashPT_LOADELF header. phdr=00000000304ef570 vaddr=0xffff888000808000, paddr=0x808000, sz=0x3000 e_phnum=12 p_offset=0x808000crash_core: CrashPT_LOADELF header. phdr=000000000275e248 vaddr=0xffff88800080c000, paddr=0x80c000, sz=0x5000 e_phnum=13 p_offset=0x80c000crash_core: CrashPT_LOADELF header. phdr=000000004e47ca09 vaddr=0xffff888000900000, paddr=0x900000, sz=0xa5700000 e_phnum=14 p_offset=0x900000crash_core: CrashPT_LOADELF header. phdr=00000000e56c8350 vaddr=0xffff8880b6000000, paddr=0xb6000000, sz=0x7d51018 e_phnum=15 p_offset=0xb6000000crash_core: CrashPT_LOADELF header. phdr=0000000099d67ff3 vaddr=0xffff8880bdd51018, paddr=0xbdd51018, sz=0x27440 e_phnum=16 p_offset=0xbdd51018crash_core: CrashPT_LOADELF header. phdr=00000000461a2f21 vaddr=0xffff8880bdd78458, paddr=0xbdd78458, sz=0xbc0 e_phnum=17 p_offset=0xbdd78458crash_core: CrashPT_LOADELF header. phdr=0000000058149b54 vaddr=0xffff8880bdd79018, paddr=0xbdd79018, sz=0x9a40 e_phnum=18 p_offset=0xbdd79018crash_core: CrashPT_LOADELF header. phdr=000000001e30ff2c vaddr=0xffff8880bdd82a58, paddr=0xbdd82a58, sz=0xdbc5a8 e_phnum=19 p_offset=0xbdd82a58crash_core: CrashPT_LOADELF header. phdr=00000000e67a9768 vaddr=0xffff8880bec00000, paddr=0xbec00000, sz=0xaed000 e_phnum=20 p_offset=0xbec00000crash_core: CrashPT_LOADELF header. phdr=000000005909c4c6 vaddr=0xffff8880bf9ff000, paddr=0xbf9ff000, sz=0x453000 e_phnum=21 p_offset=0xbf9ff000crash_core: CrashPT_LOADELF header. phdr=00000000473d74ef vaddr=0xffff8880bfe58000, paddr=0xbfe58000, sz=0x64000 e_phnum=22 p_offset=0xbfe58000crash_core: CrashPT_LOADELF header. phdr=00000000abde8123 vaddr=0xffff888100000000, paddr=0x100000000, sz=0x23f000000 e_phnum=23 p_offset=0x100000000crash_core: CrashPT_LOADELF header. phdr=00000000bda3e0bf vaddr=0xffff88843f000000, paddr=0x43f000000, sz=0x1000000 e_phnum=24 p_offset=0x43f000000
kexec: Loaded ELF headers at0x33f000000bufsz=0x1000 memsz=0xe1000BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 5 UID: 0 PID: 3812 Comm: kexec Not tainted 6.14.0-rc1+ #20 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 2025.02-6 04/08/2025 RIP: 0010:sized_strscpy+0x71/0x150 Code: b9 80 80 80 80 80 80 80 80 48 c1 e8 03 48 8d 1c c5 08 00 00 00 31 c0 eb 11 48 89 34 07 48 83 c0 08 48 39 d8 0f 84 83 00 00 00 <49> 8b 34 00 4a 8d 14 1e 49 89 f2 49 f7 d2 4c 21 d2 4c 8d 14 07 4c RSP: 0018:ffffc9000420fc68 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000080 RCX: 0000000000000080 RDX: 0000000000000080 RSI: 0000000000000000 RDI: ffff8881030ec808 RBP: ffff888109724000 R08: 0000000000000000 R09: 8080808080808080 R10: ffffc9000420fc78 R11: fefefefefefefeff R12: ffffc90004219000 R13: ffff888104a80000 R14: 0000000000000008 R15: 0000000000000000 FS: 00007f09ea73f740(0000) GS:ffff88843fc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000120760002 CR4: 0000000000772ef0 PKRU: 55555554 Call Trace: <TASK> ? __die+0x23/0x60 ? page_fault_oops+0x177/0x510 ? _prb_read_valid+0x2e7/0x370 ? exc_page_fault+0x6f/0x130 ? asm_exc_page_fault+0x26/0x30 ? sized_strscpy+0x71/0x150 crash_load_dm_crypt_keys+0x1bc/0x370 bzImage64_load+0x41b/0xa30 __do_sys_kexec_file_load+0x2af/0x8a0 do_syscall_64+0x4b/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f09ea848d6d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 4889 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6b 70 0d 00 f7 d8 64 89 01 48
RSP: 002b:00007fff8cf979e8 EFLAGS: 00000206ORIG_RAX: 0000000000000140
RAX: ffffffffffffffda RBX: 0000000000000000 RCX:00007f09ea848d6d
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000003
RBP: 0000000000000003 R08:000000000000000aR09:00007fff8cf97a10
R10:000055de70eee9a0R11: 0000000000000206 R12: 0000000000000003
R13:00007fff8cf97d08R14:000055de4c336448R15: 0000000000000004</TASK> CR2: 0000000000000000 ---[ end trace 0000000000000000 ]--- RIP: 0010:sized_strscpy+0x71/0x150 Code: b9 80 80 80 80 80 80 80 80 48 c1 e8 03 48 8d 1c c5 08 00 00 00 31 c0 eb 11 48 89 34 07 48 83 c0 08 48 39 d8 0f 84 83 00 00 00 <49> 8b 34 00 4a 8d 14 1e 49 89 f2 49 f7 d2 4c 21 d2 4c 8d 14 07 4c RSP: 0018:ffffc9000420fc68 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000080 RCX: 0000000000000080 RDX: 0000000000000080 RSI: 0000000000000000 RDI: ffff8881030ec808 RBP: ffff888109724000 R08: 0000000000000000 R09: 8080808080808080 R10: ffffc9000420fc78 R11: fefefefefefefeff R12: ffffc90004219000 R13: ffff888104a80000 R14: 0000000000000008 R15: 0000000000000000 FS: 00007f09ea73f740(0000) GS:ffff88843fc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000120760002 CR4: 0000000000772ef0 PKRU: 55555554 Kernel panic - not syncing: Fatal exceptionKernel Offset: disabled
Calling a script that does the same thing works fine and loads the keys correctly:
[Service]
ExecStart=/root/kexec.sh~ # cat
/root/kexec.sh
#!/bin/bashmkdir
/sys/kernel/config/crash_dm_crypt_keys/mykey
echo cryptsetup:mykey >/sys/kernel/config/crash_dm_crypt_keys/mykey/description/usr/host/bin/kexec--debug --load-panic /linux-hv --initrd /crash-initrdIf that's any help, my crypttab:
~ # cat
/etc/crypttab
root UUID=8001fca4-2e54-48e9-9235-031c19fc6e36 none luks,link-volume-key=@u::%logon:cryptsetup:mykeyIf you can't reproduce, I can help track this. Just let me know if you need any help.
Signature · 2 lines
Best regards, Coiby
Quoted 106 lines · Arnaud Lefebvre
Quoted 70 lines · Coiby Xu
Quoted 69 lines · Arnaud Lefebvre
Quoted 67 lines · Coiby Xu
LUKS is the standard for Linux disk encryption, widely adopted by users, and in some cases, such as Confidential VMs, it is a requirement. With kdump enabled, when the first kernel crashes, the system can boot into the kdump/crash kernel to dump the memory image (i.e.,
/proc/vmcore) to a specified target. However, there are two challenges when dumping vmcore to a LUKS-encrypted device:- Kdump kernel may not be able to decrypt the LUKS partition. For some machines, a system administrator may not have a chance to enter the password to decrypt the device in kdump initramfs after the 1st kernel crashes; For cloud confidential VMs, depending on the policy the kdump kernel may not be able to unseal the keys with TPM and the console virtual keyboard is untrusted.
- LUKS2 by default use the memory-hard Argon2 key derivation function which is quite memory-consuming compared to the limited memory reserved for kdump. Take Fedora example, by default, only 256M is reserved for systems having memory between 4G-64G. With LUKS enabled, ~1300M needs to be reserved for kdump. Note if the memory reserved for kdump can't be used by 1st kernel i.e. an user sees ~1300M memory missing in the 1st kernel.
Besides users (at least for Fedora) usually expect kdump to work out of the box i.e. no manual password input or custom crashkernel value is needed. And it doesn't make sense to derivate the keys again in kdump kernel which seems to be redundant work.
This patch set addresses the above issues by making the LUKS volume keys persistent for kdump kernel with the help of cryptsetup's new APIs (--link-vk-to-keyring/--volume-key-keyring). Here is the life cycle of the kdump copies of LUKS volume keys,
1. After the 1st kernel loads the initramfs during boot, systemd use an user-input passphrase to de-crypt the LUKS volume keys or TPM-sealed key and then save the volume keys to specified keyring (using the --link-vk-to-keyring API) and the key will expire within specified time.
2. A user space tool (kdump initramfs loader like kdump-utils) create key items inside
/sys/kernel/config/crash_dm_crypt_keysto inform the 1st kernel which keys are needed.3. When the kdump initramfs is loaded by the
kexec_file_loadsyscall, the 1st kernel will iterate created key items, save the keys to kdump reserved memory.4. When the 1st kernel crashes and the kdump initramfs is booted, the kdump initramfs asks the kdump kernel to create a user key using the key stored in kdump reserved memory by writing yes to
/sys/kernel/crash_dm_crypt_keys/restore. Then the LUKS encrypted device is unlocked with libcryptsetup's --volume-key-keyring API.5. The system gets rebooted to the 1st kernel after dumping vmcore to the LUKS encrypted device is finished
After libcryptsetup saving the LUKS volume keys to specified keyring, whoever takes this should be responsible for the safety of these copies of keys. The keys will be saved in the memory area exclusively reserved for kdump where even the 1st kernel has no direct access. And further more, two additional protections are added,
- save the copy randomly in kdump reserved memory as suggested by Jan
- clear the_PAGE_PRESENTflag of the page that stores the copy as suggested by PingfanThis patch set only supports x86. There will be patches to support other architectures once this patch set gets merged.
Quoted 9 lines
Quoted 3 lines
I'm not sure what's the problem here but I can reliably trigger a kernel panic on a qemu VM + custom kernel (compiled from
bb066fe812d6fb3a9d01c073d9f1e2fd5a63403b+ your patches).Hi Arnaud,
Thanks for testing the patches, finding this issue and also sharing the details to reproduce it!
Hello,
You're welcome, thanks to you for this patch series!
Quoted 15 lines
Quoted 8 lines
When I configure the crash configfs and call kexec in a systemd service using ExecStart=, the panic occurs when I start the service:
~ # cat
/etc/systemd/system/my-kexec.service[Unit]
Description=kexec loading for the crash capture kernelQuoted 6 lines
[Service]
Type=oneshot
ExecStart=/usr/bin/mkdir/sys/kernel/config/crash_dm_crypt_keys/mykeyExecStart=/usr/bin/echo cryptsetup:mykey >/sys/kernel/config/crash_dm_crypt_keys/mykey/description ExecStart=/usr/host/bin/kexec --debug --load-panic /linux-hv --initrd /crash-initrd KeyringMode=sharedQuoted 5 lines
Can you try putting the above commands into a script e.g.
/usr/local/bin/my-kexec.shand then using ExecStart=/usr/local/bin/my-kexec.sh
so I can be more sure that I've reproduced your issue?
Quoted 4 lines
I believe that's what I wrote at the end of my previous message (see below the panic trace). It works fine using a script like that.
Did you miss it or is there a difference with what you're asking?
Oh, I missed it, thanks for the reminder! Now I'm sure I have reproduced the issue and understood how the problem happens. This is because systemd will ignore the bash redirection ">" as it doesn't invoke bash to run ExecStart. So you will see systemd logs as follows,
warning: ignoring excess arguments, starting with with ‘>/sys/kernel/config/...
So a key configfs item is created but the key description fails to be set. Unfortunately, the kernel doesn't check if the key description is null and crashes when trying to copy it. I'll send a new version of patches to resolve this issue, thanks!
Quoted 33 lines
[...]
Quoted 30 lines
Quoted 25 lines
Kernel panic - not syncing: Fatal exceptionKernel Offset: disabled
Calling a script that does the same thing works fine and loads the keys correctly:
[Service]
ExecStart=/root/kexec.sh~ # cat
/root/kexec.sh
#!/bin/bashmkdir
/sys/kernel/config/crash_dm_crypt_keys/mykey
echo cryptsetup:mykey >/sys/kernel/config/crash_dm_crypt_keys/mykey/description/usr/host/bin/kexec--debug --load-panic /linux-hv --initrd /crash-initrdIf that's any help, my crypttab:
~ # cat
/etc/crypttab
root UUID=8001fca4-2e54-48e9-9235-031c19fc6e36 none luks,link-volume-key=@u::%logon:cryptsetup:mykeyIf you can't reproduce, I can help track this. Just let me know if you need any help.
Signature · 2 lines
Best regards, Coiby
Signature · 2 lines
Best regards, Coiby