[PATCH v18 11/11] arm64: Enable passing IMA log to next kernel on kexec

Update CONFIG_KEXEC_FILE to select CONFIG_HAVE_IMA_KEXEC, if CONFIG_IMA is enabled, to indicate that the IMA measurement log information is present in the device tree for ARM64. Co-developed-by: Prakhar Srivastava Signed-off-by: Prakhar Srivastava Signed-off-by: Lakshmi Ramasubramanian

[PATCH v18 10/11] powerpc: Delete unused function delete_fdt_mem_rsv()

delete_fdt_mem_rsv() defined in "arch/powerpc/kexec/file_load.c" has been renamed to fdt_find_and_del_mem_rsv(), and moved to "drivers/of/kexec.c". Remove delete_fdt_mem_rsv() in "arch/powerpc/kexec/file_load.c". Co-developed-by: Prakhar Srivastava Signed-off-by: Prakhar Srivastava

[PATCH v18 09/11] kexec: Use fdt_appendprop_addrrange() to add ima buffer to FDT

fdt_appendprop_addrrange() function adds a property, with the given name, to the device tree at the given node offset, and also sets the address and size of the property. This function should be used to add "linux,ima-kexec-buffer" property to the device tree and set the address and size of the

[PATCH v18 08/11] powerpc: Move arch independent ima kexec functions to drivers/of/kexec.c

The functions defined in "arch/powerpc/kexec/ima.c" handle setting up and freeing the resources required to carry over the IMA measurement list from the current kernel to the next kernel across kexec system call. These functions do not have architecture specific code, but are currently limited to

[PATCH v18 07/11] powerpc: Enable passing IMA log to next kernel on kexec

CONFIG_HAVE_IMA_KEXEC is enabled to indicate that the IMA measurement log information is present in the device tree. This should be selected only if CONFIG_IMA is enabled. Update CONFIG_KEXEC_FILE to select CONFIG_HAVE_IMA_KEXEC, if CONFIG_IMA is enabled, to indicate that the IMA measurement log

[PATCH v18 05/11] powerpc: Use common of_kexec_alloc_and_setup_fdt()

From: Rob Herring The code for setting up the /chosen node in the device tree and updating the memory reservation for the next kernel has been moved to of_kexec_alloc_and_setup_fdt() defined in "drivers/of/kexec.c". Use the common of_kexec_alloc_and_setup_fdt() to setup the device tree and

[PATCH v18 06/11] powerpc: Move ima buffer fields to struct kimage

The fields ima_buffer_addr and ima_buffer_size in "struct kimage_arch" for powerpc are used to carry forward the IMA measurement list across kexec system call. These fields are not architecture specific, but are currently limited to powerpc. arch_ima_add_kexec_buffer() defined in

[PATCH v18 01/11] powerpc: Rename kexec elfcorehdr_addr to elf_load_addr

From: Rob Herring The architecture specific field, elfcorehdr_addr in struct kimage_arch, that holds the address of the buffer in memory for ELF core header for powerpc has a different name than the one used for x86_64. This makes it hard to have a common code for setting up the device tree for

[PATCH v18 02/11] arm64: Rename kexec elf_headers_mem to elf_load_addr

The architecture specific field, elf_headers_mem in struct kimage_arch, that holds the address of the buffer in memory for ELF core header for arm64 has a different name than the one used for powerpc. This makes it hard to have a common code for setting up the device tree for kexec system call.

[PATCH v18 04/11] arm64: Use common of_kexec_alloc_and_setup_fdt()

From: Rob Herring The code for setting up the /chosen node in the device tree and updating the memory reservation for the next kernel has been moved to of_kexec_alloc_and_setup_fdt() defined in "drivers/of/kexec.c". Use the common of_kexec_alloc_and_setup_fdt() to setup the device tree and

[PATCH v18 00/10] Carry forward IMA measurement log on kexec on ARM64

On kexec file load Integrity Measurement Architecture (IMA) subsystem may verify the IMA signature of the kernel and initramfs, and measure it. The command line parameters passed to the kernel in the kexec call may also be measured by IMA. A remote attestation service can verify a TPM quote

[PATCH v18 03/11] of: Add a common kexec FDT setup function

From: Rob Herring Both arm64 and powerpc do essentially the same FDT /chosen setup for kexec. The differences are either omissions that arm64 should have or additional properties that will be ignored. The setup code can be combined and shared by both powerpc and arm64. The differences

[powerpc:next-test] BUILD SUCCESS ce7218f40a32592aeba98e957cdf1f61387df16a

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next-test branch HEAD: ce7218f40a32592aeba98e957cdf1f61387df16a powerpc/mm/64s: Allow STRICT_KERNEL_RWX again elapsed time: 2228m configs tested: 202 configs skipped: 2 The following configs have been built

[powerpc:next] BUILD SUCCESS 82d2c16b350f72aa21ac2a6860c542aa4b43a51e

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next branch HEAD: 82d2c16b350f72aa21ac2a6860c542aa4b43a51e powerpc/perf: Adds support for programming of Thresholding in P10 elapsed time: 2826m configs tested: 218 configs skipped: 2 The following configs have

[powerpc:merge] BUILD SUCCESS 463d77b1993642f56ce6929be97c08ef065f48ba

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git merge branch HEAD: 463d77b1993642f56ce6929be97c08ef065f48ba Automatic merge of 'next' into merge (2021-02-12 00:44) elapsed time: 2807m configs tested: 205 configs skipped: 3 The following configs have been built

[PATCH 4/4] ASoC: fsl: drop unneeded snd_soc_dai_set_drvdata

snd_soc_dai_set_drvdata is not needed when the set data comes from snd_soc_dai_get_drvdata or dev_get_drvdata. The problem was fixed usingthe following semantic patch: (http://coccinelle.lip6.fr/) // @@ expression x,y,e; @@ x = dev_get_drvdata(y->dev) ... when != x = e -