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
the measurement through the IMA log and the TPM PCR data. This can be
achieved only if the IMA measurement log is carried over from
the current kernel to the next kernel across the kexec call.
However in the current implementation the IMA measurement logs are not
carried over on ARM64 platforms. Therefore a remote attestation service
cannot verify the authenticity of the running kernel on ARM64 platforms
when the kernel is updated through the kexec system call.
This patch series adds support for carrying forward the IMA measurement
log on kexec on ARM64. powerpc already supports carrying forward
the IMA measurement log on kexec.
This series refactors the platform independent code defined for powerpc
such that it can be reused for ARM64 as well. A chosen node namely
"linux,ima-kexec-buffer" is added to the DTB for ARM64 to hold
the address and the size of the memory reserved to carry
the IMA measurement log.
This patch series has been tested for ARM64 platform using QEMU.
I would like help from the community for testing this change on powerpc.
Thanks.
This patch series is based on
commit 598a597636f8 ("Merge tag 'afs-fixes-20201029' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs")
in https://github.com/torvalds/linux "master" branch.
Changelog:
v8:
- Moved remove_ima_kexec_buffer(), do_get_kexec_buffer(), and
delete_fdt_mem_rsv() to drivers/of/fdt.c
- Moved ima_dump_measurement_list() and ima_add_kexec_buffer()
back to security/integrity/ima/ima_kexec.c
v7:
- Renamed remove_ima_buffer() to remove_ima_kexec_buffer() and moved
this function definition to kernel.
- Moved delete_fdt_mem_rsv() definition to kernel
- Moved ima_dump_measurement_list() and ima_add_kexec_buffer() to
a new file namely ima_kexec_fdt.c in IMA
v6:
- Remove any existing FDT_PROP_IMA_KEXEC_BUFFER property in the device
tree and also its corresponding memory reservation in the currently
running kernel.
- Moved the function remove_ima_buffer() defined for powerpc to IMA
and renamed the function to ima_remove_kexec_buffer(). Also, moved
delete_fdt_mem_rsv() from powerpc to IMA.
v5:
- Merged get_addr_size_cells() and do_get_kexec_buffer() into a single
function when moving the arch independent code from powerpc to IMA
- Reverted the change to use FDT functions in powerpc code and added
back the original code in get_addr_size_cells() and
do_get_kexec_buffer() for powerpc.
- Added fdt_add_mem_rsv() for ARM64 to reserve the memory for
the IMA log buffer during kexec.
- Fixed the warning reported by kernel test bot for ARM64
arch_ima_add_kexec_buffer() - moved this function to a new file
namely arch/arm64/kernel/ima_kexec.c
v4:
- Submitting the patch series on behalf of the original author
Prakhar Srivastava [off-list ref]
- Moved FDT_PROP_IMA_KEXEC_BUFFER ("linux,ima-kexec-buffer") to
libfdt.h so that it can be shared by multiple platforms.
v3:
Breakup patches further into separate patches.
- Refactoring non architecture specific code out of powerpc
- Update powerpc related code to use fdt functions
- Update IMA buffer read related code to use of functions
- Add support to store the memory information of the IMA
measurement logs to be carried forward.
- Update the property strings to align with documented nodes
https://github.com/devicetree-org/dt-schema/pull/46
v2:
Break patches into separate patches.
- Powerpc related Refactoring
- Updating the docuemntation for chosen node
- Updating arm64 to support IMA buffer pass
v1:
Refactoring carrying over IMA measuremnet logs over Kexec. This patch
moves the non-architecture specific code out of powerpc and adds to
security/ima.(Suggested by Thiago)
Add Documentation regarding the ima-kexec-buffer node in the chosen
node documentation
v0:
Add a layer of abstraction to use the memory reserved by device tree
for ima buffer pass.
Add support for ima buffer pass using reserved memory for arm64 kexec.
Update the arch sepcific code path in kexec file load to store the
ima buffer in the reserved memory. The same reserved memory is read
on kexec or cold boot.
Lakshmi Ramasubramanian (4):
powerpc: Refactor kexec functions to move arch independent code to
drivers/of
powerpc: Refactor kexec functions to move arch independent code to ima
arm64: Store IMA log information in kimage used for kexec
arm64: Add IMA kexec buffer to DTB
arch/arm64/Kconfig | 1 +
arch/arm64/include/asm/ima.h | 18 ++++
arch/arm64/include/asm/kexec.h | 3 +
arch/arm64/kernel/Makefile | 1 +
arch/arm64/kernel/ima_kexec.c | 34 ++++++++
arch/arm64/kernel/machine_kexec_file.c | 18 ++++
arch/powerpc/include/asm/ima.h | 13 +--
arch/powerpc/include/asm/kexec.h | 1 -
arch/powerpc/kexec/Makefile | 7 +-
arch/powerpc/kexec/file_load.c | 33 +-------
arch/powerpc/kexec/ima.c | 111 ++-----------------------
drivers/of/fdt.c | 110 ++++++++++++++++++++++++
include/linux/kexec.h | 24 ++++++
include/linux/libfdt.h | 3 +
security/integrity/ima/ima_kexec.c | 57 +++++++++++++
15 files changed, 282 insertions(+), 152 deletions(-)
create mode 100644 arch/arm64/include/asm/ima.h
create mode 100644 arch/arm64/kernel/ima_kexec.c
--
2.29.0
The functions ima_get_kexec_buffer() and ima_free_kexec_buffer(),
that handle carrying forward the IMA measurement logs on kexec for
powerpc do not have architecture specific code, but they are currently
defined for powerpc only.
Move ima_get_kexec_buffer() and ima_free_kexec_buffer() to IMA
subsystem. A later patch in this series will use these functions for
carrying forward the IMA measurement log for ARM64.
With the above refactoring arch/powerpc/kexec/ima.c contains only
functions used when CONFIG_IMA_KEXEC is enabled. Update Makefile
in arch/powerpc/kexec to include arch/powerpc/kexec/ima.c only
when CONFIG_IMA_KEXEC is enabled.
Co-developed-by: Prakhar Srivastava <redacted>
Signed-off-by: Prakhar Srivastava <redacted>
Signed-off-by: Lakshmi Ramasubramanian <redacted>
---
arch/powerpc/include/asm/ima.h | 3 --
arch/powerpc/kexec/Makefile | 7 +---
arch/powerpc/kexec/ima.c | 56 -----------------------------
security/integrity/ima/ima_kexec.c | 57 ++++++++++++++++++++++++++++++
4 files changed, 58 insertions(+), 65 deletions(-)
Address and size of the buffer containing the IMA measurement log need
to be passed from the current kernel to the next kernel on kexec.
Add address and size fields to "struct kimage_arch" for ARM64 platform
to hold the address and size of the IMA measurement log buffer.
Define an architecture specific function for ARM64 namely
arch_ima_add_kexec_buffer() that will set the address and size of
the current kernel's IMA buffer to be passed to the next kernel on kexec.
Co-developed-by: Prakhar Srivastava <redacted>
Signed-off-by: Prakhar Srivastava <redacted>
Signed-off-by: Lakshmi Ramasubramanian <redacted>
Reviewed-by: Thiago Jung Bauermann <redacted>
---
arch/arm64/include/asm/ima.h | 18 ++++++++++++++++++
arch/arm64/include/asm/kexec.h | 3 +++
arch/arm64/kernel/Makefile | 1 +
arch/arm64/kernel/ima_kexec.c | 34 ++++++++++++++++++++++++++++++++++
4 files changed, 56 insertions(+)
create mode 100644 arch/arm64/include/asm/ima.h
create mode 100644 arch/arm64/kernel/ima_kexec.c
The functions remove_ima_buffer() and delete_fdt_mem_rsv() that handle
carrying forward the IMA measurement logs on kexec for powerpc do not
have architecture specific code, but they are currently defined for
powerpc only.
remove_ima_buffer() and delete_fdt_mem_rsv() are used to remove
the IMA log entry from the device tree and free the memory reserved
for the log. These functions need to be defined even if the current
kernel does not support carrying forward IMA log across kexec since
the previous kernel could have supported that and therefore the current
kernel needs to free the allocation.
Rename remove_ima_buffer() to remove_ima_kexec_buffer().
Define remove_ima_kexec_buffer() and delete_fdt_mem_rsv() in
drivers/of/fdt.c. A later patch in this series will use these functions
to free the allocation, if any, made by the previous kernel for ARM64.
Define FDT_PROP_IMA_KEXEC_BUFFER for the chosen node, namely
"linux,ima-kexec-buffer", that is added to the DTB to hold
the address and the size of the memory reserved to carry
the IMA measurement log.
Co-developed-by: Prakhar Srivastava <redacted>
Signed-off-by: Prakhar Srivastava <redacted>
Signed-off-by: Lakshmi Ramasubramanian <redacted>
Reported-by: kernel test robot <redacted> error: kernel/kexec_file_fdt.c:30: undefined reference to `fdt_num_mem_rsv'
---
arch/powerpc/include/asm/ima.h | 10 +--
arch/powerpc/include/asm/kexec.h | 1 -
arch/powerpc/kexec/file_load.c | 33 +---------
arch/powerpc/kexec/ima.c | 55 +++-------------
drivers/of/fdt.c | 110 +++++++++++++++++++++++++++++++
include/linux/kexec.h | 24 +++++++
include/linux/libfdt.h | 3 +
7 files changed, 149 insertions(+), 87 deletions(-)
@@ -28,24 +30,6 @@ static int get_addr_size_cells(int *addr_cells, int *size_cells)return0;}-staticintdo_get_kexec_buffer(constvoid*prop,intlen,unsignedlong*addr,-size_t*size)-{-intret,addr_cells,size_cells;--ret=get_addr_size_cells(&addr_cells,&size_cells);-if(ret)-returnret;--if(len<4*(addr_cells+size_cells))-return-ENOENT;--*addr=of_read_number(prop,addr_cells);-*size=of_read_number(prop+4*addr_cells,size_cells);--return0;-}-/***ima_get_kexec_buffer-getIMAbufferfromthepreviouskernel*@addr:Onsuccessfulreturn,settopointtothebuffercontents.
@@ -100,37 +84,14 @@ int ima_free_kexec_buffer(void)}-/**-*remove_ima_buffer-removetheIMAbufferpropertyandreservationfrom@fdt-*-*TheIMAmeasurementbufferisofnousetoasubsequentkernel,sowealways-*removeitfromthedevicetree.-*/-voidremove_ima_buffer(void*fdt,intchosen_node)-{-intret,len;-unsignedlongaddr;-size_tsize;-constvoid*prop;--prop=fdt_getprop(fdt,chosen_node,"linux,ima-kexec-buffer",&len);-if(!prop)-return;--ret=do_get_kexec_buffer(prop,len,&addr,&size);-fdt_delprop(fdt,chosen_node,"linux,ima-kexec-buffer");-if(ret)-return;--ret=delete_fdt_mem_rsv(fdt,addr,size);-if(!ret)-pr_debug("Removed old IMA buffer reservation.\n");-}-#ifdef CONFIG_IMA_KEXEC/***arch_ima_add_kexec_buffer-doarch-specificstepstoaddtheIMAbuffer*+*@image:kimagestructtosetIMAbufferdata+*@load_addr:StartingaddresswhereIMAbufferisloadedat+*@size:NumberofbytesintheIMAbuffer+**ArchitecturesshouldusethisfunctiontopassontheIMAbuffer*informationtothenextkernel.*
@@ -179,7 +140,7 @@ int setup_ima_buffer(const struct kimage *image, void *fdt, int chosen_node)intret,addr_cells,size_cells,entry_size;u8value[16];-remove_ima_buffer(fdt,chosen_node);+remove_ima_kexec_buffer(fdt,chosen_node);if(!image->arch.ima_buffer_size)return0;
@@ -201,7 +162,7 @@ int setup_ima_buffer(const struct kimage *image, void *fdt, int chosen_node)if(ret)returnret;-ret=fdt_setprop(fdt,chosen_node,"linux,ima-kexec-buffer",value,+ret=fdt_setprop(fdt,chosen_node,FDT_PROP_IMA_KEXEC_BUFFER,value,entry_size);if(ret<0)return-EINVAL;
@@ -25,6 +25,7 @@#include<linux/serial_core.h>#include<linux/sysfs.h>#include<linux/random.h>+#include<linux/kexec.h>#include<asm/setup.h> /* for COMMAND_LINE_SIZE */#include<asm/page.h>
@@ -1289,4 +1290,113 @@ static int __init of_fdt_raw_init(void)late_initcall(of_fdt_raw_init);#endif+#ifdef CONFIG_HAVE_IMA_KEXEC+/**+*do_get_kexec_buffer-GetaddressandsizeofIMAkexecbuffer+*+*@prop:IMAkexecbuffernodeinthedevicetree+*@len:Sizeofthegivendevicetreenodeproperty+*@addr:Returnaddressofthenode+*@size:Returnsizeofthenode+*/+intdo_get_kexec_buffer(constvoid*prop,intlen,unsignedlong*addr,+size_t*size)+{+intaddr_cells,size_cells;+structdevice_node*root;++root=of_find_node_by_path("/");+if(!root)+return-EINVAL;++addr_cells=of_n_addr_cells(root);+size_cells=of_n_size_cells(root);++of_node_put(root);++if(len<4*(addr_cells+size_cells))+return-ENOENT;++*addr=of_read_number(prop,addr_cells);+*size=of_read_number(prop+4*addr_cells,size_cells);++return0;+}++/**+*remove_ima_kexec_buffer-removetheIMAbufferpropertyand+*reservationfrom@fdt+*+*@fdt:FlattenedDeviceTreetoupdate+*@chosen_node:Offsettothechosennodeinthedevicetree+*+*TheIMAmeasurementbufferisofnousetoasubsequentkernel,+*sowealwaysremoveitfromthedevicetree.+*/+voidremove_ima_kexec_buffer(void*fdt,intchosen_node)+{+intret,len;+unsignedlongaddr;+size_tsize;+constvoid*prop;++prop=fdt_getprop(fdt,chosen_node,FDT_PROP_IMA_KEXEC_BUFFER,&len);+if(!prop){+pr_debug("Unable to find the ima kexec buffer node\n");+return;+}++ret=do_get_kexec_buffer(prop,len,&addr,&size);+fdt_delprop(fdt,chosen_node,FDT_PROP_IMA_KEXEC_BUFFER);+if(ret){+pr_err("Unable to delete the ima kexec buffer node\n");+return;+}++ret=delete_fdt_mem_rsv(fdt,addr,size);+if(!ret)+pr_debug("Removed old IMA buffer reservation.\n");+}+#endif /* CONFIG_HAVE_IMA_KEXEC */++#ifdef CONFIG_KEXEC_FILE+/**+*delete_fdt_mem_rsv-deletememoryreservationwithgivenaddressandsize+*+*@fdt:FlattenedDeviceTreetoupdate+*@start:Startingaddressofthereservationtodelete+*@size:Sizeofthereservationtodelete+*+*Return:0onsuccess,ornegativeerrnoonerror.+*/+intdelete_fdt_mem_rsv(void*fdt,unsignedlongstart,unsignedlongsize)+{+inti,ret,num_rsvs=fdt_num_mem_rsv(fdt);++for(i=0;i<num_rsvs;i++){+uint64_trsv_start,rsv_size;++ret=fdt_get_mem_rsv(fdt,i,&rsv_start,&rsv_size);+if(ret){+pr_err("Malformed device tree.\n");+return-EINVAL;+}++if(rsv_start==start&&rsv_size==size){+ret=fdt_del_mem_rsv(fdt,i);+if(ret){+pr_err("Error deleting device tree reservation.\n");+return-EINVAL;+}++pr_debug("Freed reserved memory at %lu of size %lu\n",+start,size);+return0;+}+}++return-ENOENT;+}+#endif /* CONFIG_KEXEC_FILE */+#endif /* CONFIG_OF_EARLY_FLATTREE */
Any existing FDT_PROP_IMA_KEXEC_BUFFER property in the device tree
needs to be removed and its corresponding memory reservation in
the currently running kernel needs to be freed.
The address and size of the current kernel's IMA measurement log need
to be added to the device tree's IMA kexec buffer node and memory for
the buffer needs to be reserved for the log to be carried over to
the next kernel on the kexec call.
Remove any existing FDT_PROP_IMA_KEXEC_BUFFER property in the device
tree and free the corresponding memory reservation in the currently
running kernel. Add FDT_PROP_IMA_KEXEC_BUFFER property to the device
tree and reserve the memory for storing the IMA log that needs to be
passed from the current kernel to the next one.
Update CONFIG_KEXEC_FILE to select CONFIG_HAVE_IMA_KEXEC to indicate
that the IMA measurement log information is present in the device tree
for ARM64.
Co-developed-by: Prakhar Srivastava <redacted>
Signed-off-by: Prakhar Srivastava <redacted>
Signed-off-by: Lakshmi Ramasubramanian <redacted>
Reviewed-by: Thiago Jung Bauermann <redacted>
---
arch/arm64/Kconfig | 1 +
arch/arm64/kernel/machine_kexec_file.c | 18 ++++++++++++++++++
2 files changed, 19 insertions(+)
@@ -1074,6 +1074,7 @@ config KEXECconfigKEXEC_FILEbool"kexec file based system call"selectKEXEC_CORE+selectHAVE_IMA_KEXEChelpThisisnewversionofkexecsystemcall.Thissystemcallisfilebasedandtakesfiledescriptorsassystemcallargument
Hi Lakshmi,
On Fri, 2020-10-30 at 10:44 -0700, Lakshmi Ramasubramanian wrote:
The functions remove_ima_buffer() and delete_fdt_mem_rsv() that handle
carrying forward the IMA measurement logs on kexec for powerpc do not
have architecture specific code, but they are currently defined for
powerpc only.
^ ... logs on kexec, do not have architecture specific code, but are
currently limited to powerpc.
remove_ima_buffer() and delete_fdt_mem_rsv() are used to remove
the IMA log entry from the device tree and free the memory reserved
for the log. These functions need to be defined even if the current
kernel does not support carrying forward IMA log across kexec since
the previous kernel could have supported that and therefore the current
kernel needs to free the allocation.
The first paragraph describes these function as "handle carrying
forward the IMA measurement logs on kexec", while this paragraph says
"are used to remove the IMA log entry". Consider listing all of the
functions being moved in the first paragrah, then "handle carrying
forward" could be expanded to "carrying ... and removing".
Rename remove_ima_buffer() to remove_ima_kexec_buffer().
Define remove_ima_kexec_buffer() and delete_fdt_mem_rsv() in
drivers/of/fdt.c. A later patch in this series will use these functions
to free the allocation, if any, made by the previous kernel for ARM64.
- ^Define -> Move
- Three functions are being moved, but only two are listed.
"do_get_kexec_buffer" is not mentioned.
- Don't refer to a later patch, but explain the purpose here. For
example, "Move ... , making them accessible to other archs."
Define FDT_PROP_IMA_KEXEC_BUFFER for the chosen node, namely
"linux,ima-kexec-buffer", that is added to the DTB to hold
the address and the size of the memory reserved to carry
the IMA measurement log.
The above two paragraphs describe renaming a function and defining a
chosen node. These two preparatory changes should be made,
independently of each other, prior to this patch. This patch should be
limited to moving code, with the subject line truncated to "move arch
independent code to drivers/of".
thanks,
Mimi
Hi Lakshmi,
On Fri, 2020-10-30 at 10:44 -0700, Lakshmi Ramasubramanian wrote:
The functions ima_get_kexec_buffer() and ima_free_kexec_buffer(),
that handle carrying forward the IMA measurement logs on kexec for
powerpc do not have architecture specific code, but they are currently
defined for powerpc only.
Move ima_get_kexec_buffer() and ima_free_kexec_buffer() to IMA
subsystem. A later patch in this series will use these functions for
carrying forward the IMA measurement log for ARM64.
With the above refactoring arch/powerpc/kexec/ima.c contains only
functions used when CONFIG_IMA_KEXEC is enabled. Update Makefile
in arch/powerpc/kexec to include arch/powerpc/kexec/ima.c only
when CONFIG_IMA_KEXEC is enabled.
Co-developed-by: Prakhar Srivastava <redacted>
Signed-off-by: Prakhar Srivastava <redacted>
Signed-off-by: Lakshmi Ramasubramanian <redacted>
Similar comments to 1/4.
- Last line of first paragraph can be rephrased like " ... on kexec,
do not contain architecture specific code, but are currently limited to
powerpc."
- This patch should be limited to moving existing functions.
Truncate the Subject line to "Move arch independent IMA kexec functions
to ima_kexec.c."
- Don't refer to a later patch, but explain the purpose here. For
example, "Move ... , making them accessible to other archs."
- The definition of "FDT_PROP_IMA_KEXEC_BUFFER" should be made as a
separate, prepartory patch, prior to the existing 1/4. The resulting
code being moved in this patch (and similarly for 1/4) will be exactly
the same as the code being deleted.
thanks,
Mimi
On Fri, 2020-10-30 at 10:44 -0700, Lakshmi Ramasubramanian wrote:
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
the measurement through the IMA log and the TPM PCR data. This can be
achieved only if the IMA measurement log is carried over from
the current kernel to the next kernel across the kexec call.
Nice, but you might want to tweak it a bit. This is just a suggestion.
"A remote attestation service can verify a TPM quote based on the TPM
event log, the IMA measurement list, and the TPM PCR data".
However in the current implementation the IMA measurement logs are not
carried over on ARM64 platforms. Therefore a remote attestation service
cannot verify the authenticity of the running kernel on ARM64 platforms
when the kernel is updated through the kexec system call.
The paragraphs above and below are redundant. The first paragraph
already explained why carrying the measurement across kexec is needed.
Perhaps drop the above paragraph.
This patch series adds support for carrying forward the IMA measurement
log on kexec on ARM64. powerpc already supports carrying forward
the IMA measurement log on kexec.
And invert these sentences, starting the paragraph with "Powerpc
already" and ending with ARM64.
This series refactors the platform independent code defined for powerpc
such that it can be reused for ARM64 as well. A chosen node namely
"linux,ima-kexec-buffer" is added to the DTB for ARM64 to hold
the address and the size of the memory reserved to carry
the IMA measurement log.
^This patch set moves ..."
Thanks,
Mimi
This patch series has been tested for ARM64 platform using QEMU.
I would like help from the community for testing this change on powerpc.
Thanks.
This patch series is based on
commit 598a597636f8 ("Merge tag 'afs-fixes-20201029' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs")
in https://github.com/torvalds/linux "master" branch.
On 11/3/20 6:55 AM, Mimi Zohar wrote:
Hi Mimi,
Thanks for reviewing the patches.
On Fri, 2020-10-30 at 10:44 -0700, Lakshmi Ramasubramanian wrote:
quoted
The functions remove_ima_buffer() and delete_fdt_mem_rsv() that handle
carrying forward the IMA measurement logs on kexec for powerpc do not
have architecture specific code, but they are currently defined for
powerpc only.
^ ... logs on kexec, do not have architecture specific code, but are
currently limited to powerpc.
Will make this change.
quoted
remove_ima_buffer() and delete_fdt_mem_rsv() are used to remove
the IMA log entry from the device tree and free the memory reserved
for the log. These functions need to be defined even if the current
kernel does not support carrying forward IMA log across kexec since
the previous kernel could have supported that and therefore the current
kernel needs to free the allocation.
The first paragraph describes these function as "handle carrying
forward the IMA measurement logs on kexec", while this paragraph says
"are used to remove the IMA log entry". Consider listing all of the
functions being moved in the first paragrah, then "handle carrying
forward" could be expanded to "carrying ... and removing".
Sure.
quoted
Rename remove_ima_buffer() to remove_ima_kexec_buffer().
Define remove_ima_kexec_buffer() and delete_fdt_mem_rsv() in
drivers/of/fdt.c. A later patch in this series will use these functions
to free the allocation, if any, made by the previous kernel for ARM64.
- ^Define -> Move
- Three functions are being moved, but only two are listed.
"do_get_kexec_buffer" is not mentioned.
- Don't refer to a later patch, but explain the purpose here. For
example, "Move ... , making them accessible to other archs."
Sure.
quoted
Define FDT_PROP_IMA_KEXEC_BUFFER for the chosen node, namely
"linux,ima-kexec-buffer", that is added to the DTB to hold
the address and the size of the memory reserved to carry
the IMA measurement log.
The above two paragraphs describe renaming a function and defining a
chosen node. These two preparatory changes should be made,
independently of each other, prior to this patch. This patch should be
limited to moving code, with the subject line truncated to "move arch
independent code to drivers/of".
Just to be clear -
Split this patch into 3 parts as listed below:
PATCH #1: Rename remove_ima_buffer() to remove_ima_kexec_buffer()
PATCH #2: Define the chosen node
PATCH #3: Move the functions to drivers/of/fdt.c
Sure - I'll make the above changes and update patch descriptions
accordingly.
thanks,
-lakshmi
On Fri, 2020-10-30 at 10:44 -0700, Lakshmi Ramasubramanian wrote:
quoted
The functions ima_get_kexec_buffer() and ima_free_kexec_buffer(),
that handle carrying forward the IMA measurement logs on kexec for
powerpc do not have architecture specific code, but they are currently
defined for powerpc only.
Move ima_get_kexec_buffer() and ima_free_kexec_buffer() to IMA
subsystem. A later patch in this series will use these functions for
carrying forward the IMA measurement log for ARM64.
With the above refactoring arch/powerpc/kexec/ima.c contains only
functions used when CONFIG_IMA_KEXEC is enabled. Update Makefile
in arch/powerpc/kexec to include arch/powerpc/kexec/ima.c only
when CONFIG_IMA_KEXEC is enabled.
Co-developed-by: Prakhar Srivastava <redacted>
Signed-off-by: Prakhar Srivastava <redacted>
Signed-off-by: Lakshmi Ramasubramanian <redacted>
Similar comments to 1/4.
- Last line of first paragraph can be rephrased like " ... on kexec,
do not contain architecture specific code, but are currently limited to
powerpc."
Sure.
- This patch should be limited to moving existing functions.
Truncate the Subject line to "Move arch independent IMA kexec functions
to ima_kexec.c."
Will do.
- Don't refer to a later patch, but explain the purpose here. For
example, "Move ... , making them accessible to other archs."
Sure.
- The definition of "FDT_PROP_IMA_KEXEC_BUFFER" should be made as a
separate, prepartory patch, prior to the existing 1/4. The resulting
code being moved in this patch (and similarly for 1/4) will be exactly
the same as the code being deleted.
Definition of FDT_PROP_IMA_KEXEC_BUFFER will be made as a preparatory
patch as you'd mentioned in the comments for [PATCH 1/4].
Will split [PATCH 2/4] as listed below:
PATCH #1: Move ima_get_kexec_buffer() and ima_free_kexec_buffer() to
IMA, along with deleting them in arch/powerpc/kexec/ima.c
PATCH #2: Update arch/powerpc/kexec/Makefile and
arch/powerpc/kexec/ima.c
to compile when CONFIG_IMA_KEXEC is defined.
thanks,
-lakshmi
On Fri, 2020-10-30 at 10:44 -0700, Lakshmi Ramasubramanian wrote:
quoted
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
the measurement through the IMA log and the TPM PCR data. This can be
achieved only if the IMA measurement log is carried over from
the current kernel to the next kernel across the kexec call.
Nice, but you might want to tweak it a bit. This is just a suggestion.
"A remote attestation service can verify a TPM quote based on the TPM
event log, the IMA measurement list, and the TPM PCR data".
Sure - will make this change.
quoted
However in the current implementation the IMA measurement logs are not
carried over on ARM64 platforms. Therefore a remote attestation service
cannot verify the authenticity of the running kernel on ARM64 platforms
when the kernel is updated through the kexec system call.
The paragraphs above and below are redundant. The first paragraph
already explained why carrying the measurement across kexec is needed.
Perhaps drop the above paragraph.
Sure.
quoted
This patch series adds support for carrying forward the IMA measurement
log on kexec on ARM64. powerpc already supports carrying forward
the IMA measurement log on kexec.
And invert these sentences, starting the paragraph with "Powerpc
already" and ending with ARM64.
Sure.
quoted
This series refactors the platform independent code defined for powerpc
such that it can be reused for ARM64 as well. A chosen node namely
"linux,ima-kexec-buffer" is added to the DTB for ARM64 to hold
the address and the size of the memory reserved to carry
the IMA measurement log.
^This patch set moves ..."
Sure - will make this change.
Thanks again for reviewing the patches. Will post the updated patch set
shortly.
-lakshmi
On Tue, 2020-11-03 at 11:23 -0800, Lakshmi Ramasubramanian wrote:
On 11/3/20 6:55 AM, Mimi Zohar wrote:
Hi Mimi,
quoted
On Fri, 2020-10-30 at 10:44 -0700, Lakshmi Ramasubramanian wrote:
quoted
The functions ima_get_kexec_buffer() and ima_free_kexec_buffer(),
that handle carrying forward the IMA measurement logs on kexec for
powerpc do not have architecture specific code, but they are currently
defined for powerpc only.
Move ima_get_kexec_buffer() and ima_free_kexec_buffer() to IMA
subsystem. A later patch in this series will use these functions for
carrying forward the IMA measurement log for ARM64.
With the above refactoring arch/powerpc/kexec/ima.c contains only
functions used when CONFIG_IMA_KEXEC is enabled. Update Makefile
in arch/powerpc/kexec to include arch/powerpc/kexec/ima.c only
when CONFIG_IMA_KEXEC is enabled.
Co-developed-by: Prakhar Srivastava <redacted>
Signed-off-by: Prakhar Srivastava <redacted>
Signed-off-by: Lakshmi Ramasubramanian <redacted>
Similar comments to 1/4.
- Last line of first paragraph can be rephrased like " ... on kexec,
do not contain architecture specific code, but are currently limited to
powerpc."
Sure.
quoted
- This patch should be limited to moving existing functions.
Truncate the Subject line to "Move arch independent IMA kexec functions
to ima_kexec.c."
Will do.
quoted
- Don't refer to a later patch, but explain the purpose here. For
example, "Move ... , making them accessible to other archs."
Sure.
quoted
- The definition of "FDT_PROP_IMA_KEXEC_BUFFER" should be made as a
separate, prepartory patch, prior to the existing 1/4. The resulting
code being moved in this patch (and similarly for 1/4) will be exactly
the same as the code being deleted.
Definition of FDT_PROP_IMA_KEXEC_BUFFER will be made as a preparatory
patch as you'd mentioned in the comments for [PATCH 1/4].
Will split [PATCH 2/4] as listed below:
PATCH #1: Move ima_get_kexec_buffer() and ima_free_kexec_buffer() to
IMA, along with deleting them in arch/powerpc/kexec/ima.c
No, other than the comments above, this patch is fine. It moves
ima_get_kexec_buffer() and ima_free_kexec_buffer() to ima_kexec.c.
Mimi
On Tue, 2020-11-03 at 11:15 -0800, Lakshmi Ramasubramanian wrote:
On 11/3/20 6:55 AM, Mimi Zohar wrote:
Hi Mimi,
Thanks for reviewing the patches.
quoted
On Fri, 2020-10-30 at 10:44 -0700, Lakshmi Ramasubramanian wrote:
quoted
The functions remove_ima_buffer() and delete_fdt_mem_rsv() that handle
carrying forward the IMA measurement logs on kexec for powerpc do not
have architecture specific code, but they are currently defined for
powerpc only.
^ ... logs on kexec, do not have architecture specific code, but are
currently limited to powerpc.
Will make this change.
quoted
quoted
remove_ima_buffer() and delete_fdt_mem_rsv() are used to remove
the IMA log entry from the device tree and free the memory reserved
for the log. These functions need to be defined even if the current
kernel does not support carrying forward IMA log across kexec since
the previous kernel could have supported that and therefore the current
kernel needs to free the allocation.
The first paragraph describes these function as "handle carrying
forward the IMA measurement logs on kexec", while this paragraph says
"are used to remove the IMA log entry". Consider listing all of the
functions being moved in the first paragrah, then "handle carrying
forward" could be expanded to "carrying ... and removing".
Sure.
Sorry, even with naming do_get_kexec_buffer(), the measurement list
isn't being carried across kexec. Please adjust the wording.
quoted
quoted
Rename remove_ima_buffer() to remove_ima_kexec_buffer().
Define remove_ima_kexec_buffer() and delete_fdt_mem_rsv() in
drivers/of/fdt.c. A later patch in this series will use these functions
to free the allocation, if any, made by the previous kernel for ARM64.
- ^Define -> Move
- Three functions are being moved, but only two are listed.
"do_get_kexec_buffer" is not mentioned.
- Don't refer to a later patch, but explain the purpose here. For
example, "Move ... , making them accessible to other archs."
Sure.
quoted
quoted
Define FDT_PROP_IMA_KEXEC_BUFFER for the chosen node, namely
"linux,ima-kexec-buffer", that is added to the DTB to hold
the address and the size of the memory reserved to carry
the IMA measurement log.
The above two paragraphs describe renaming a function and defining a
chosen node. These two preparatory changes should be made,
independently of each other, prior to this patch. This patch should be
limited to moving code, with the subject line truncated to "move arch
independent code to drivers/of".
Just to be clear -
Split this patch into 3 parts as listed below:
PATCH #1: Rename remove_ima_buffer() to remove_ima_kexec_buffer()
PATCH #2: Define the chosen node
PATCH #3: Move the functions to drivers/of/fdt.c
yes, thanks.
Mimi
Sure - I'll make the above changes and update patch descriptions
accordingly.
On Tue, 2020-11-03 at 11:23 -0800, Lakshmi Ramasubramanian wrote:
quoted
On 11/3/20 6:55 AM, Mimi Zohar wrote:
Hi Mimi,
quoted
On Fri, 2020-10-30 at 10:44 -0700, Lakshmi Ramasubramanian wrote:
quoted
The functions ima_get_kexec_buffer() and ima_free_kexec_buffer(),
that handle carrying forward the IMA measurement logs on kexec for
powerpc do not have architecture specific code, but they are currently
defined for powerpc only.
Move ima_get_kexec_buffer() and ima_free_kexec_buffer() to IMA
subsystem. A later patch in this series will use these functions for
carrying forward the IMA measurement log for ARM64.
With the above refactoring arch/powerpc/kexec/ima.c contains only
functions used when CONFIG_IMA_KEXEC is enabled. Update Makefile
in arch/powerpc/kexec to include arch/powerpc/kexec/ima.c only
when CONFIG_IMA_KEXEC is enabled.
Co-developed-by: Prakhar Srivastava <redacted>
Signed-off-by: Prakhar Srivastava <redacted>
Signed-off-by: Lakshmi Ramasubramanian <redacted>
Similar comments to 1/4.
- Last line of first paragraph can be rephrased like " ... on kexec,
do not contain architecture specific code, but are currently limited to
powerpc."
Sure.
quoted
- This patch should be limited to moving existing functions.
Truncate the Subject line to "Move arch independent IMA kexec functions
to ima_kexec.c."
Will do.
quoted
- Don't refer to a later patch, but explain the purpose here. For
example, "Move ... , making them accessible to other archs."
Sure.
quoted
- The definition of "FDT_PROP_IMA_KEXEC_BUFFER" should be made as a
separate, prepartory patch, prior to the existing 1/4. The resulting
code being moved in this patch (and similarly for 1/4) will be exactly
the same as the code being deleted.
Definition of FDT_PROP_IMA_KEXEC_BUFFER will be made as a preparatory
patch as you'd mentioned in the comments for [PATCH 1/4].
Will split [PATCH 2/4] as listed below:
PATCH #1: Move ima_get_kexec_buffer() and ima_free_kexec_buffer() to
IMA, along with deleting them in arch/powerpc/kexec/ima.c
No, other than the comments above, this patch is fine. It moves
ima_get_kexec_buffer() and ima_free_kexec_buffer() to ima_kexec.c.
Ok - I will do the updates in the patch description only and keep the
code changes as is. Thanks for clarifying.
-lakshmi
On Tue, 2020-11-03 at 11:15 -0800, Lakshmi Ramasubramanian wrote:
quoted
On 11/3/20 6:55 AM, Mimi Zohar wrote:
Hi Mimi,
Thanks for reviewing the patches.
quoted
On Fri, 2020-10-30 at 10:44 -0700, Lakshmi Ramasubramanian wrote:
quoted
The functions remove_ima_buffer() and delete_fdt_mem_rsv() that handle
carrying forward the IMA measurement logs on kexec for powerpc do not
have architecture specific code, but they are currently defined for
powerpc only.
^ ... logs on kexec, do not have architecture specific code, but are
currently limited to powerpc.
Will make this change.
quoted
quoted
remove_ima_buffer() and delete_fdt_mem_rsv() are used to remove
the IMA log entry from the device tree and free the memory reserved
for the log. These functions need to be defined even if the current
kernel does not support carrying forward IMA log across kexec since
the previous kernel could have supported that and therefore the current
kernel needs to free the allocation.
The first paragraph describes these function as "handle carrying
forward the IMA measurement logs on kexec", while this paragraph says
"are used to remove the IMA log entry". Consider listing all of the
functions being moved in the first paragrah, then "handle carrying
forward" could be expanded to "carrying ... and removing".
Sure.
Sorry, even with naming do_get_kexec_buffer(), the measurement list
isn't being carried across kexec. Please adjust the wording.
Sure - will update.
quoted
quoted
quoted
Rename remove_ima_buffer() to remove_ima_kexec_buffer().
Define remove_ima_kexec_buffer() and delete_fdt_mem_rsv() in
drivers/of/fdt.c. A later patch in this series will use these functions
to free the allocation, if any, made by the previous kernel for ARM64.
- ^Define -> Move
- Three functions are being moved, but only two are listed.
"do_get_kexec_buffer" is not mentioned.
- Don't refer to a later patch, but explain the purpose here. For
example, "Move ... , making them accessible to other archs."
Sure.
quoted
quoted
Define FDT_PROP_IMA_KEXEC_BUFFER for the chosen node, namely
"linux,ima-kexec-buffer", that is added to the DTB to hold
the address and the size of the memory reserved to carry
the IMA measurement log.
The above two paragraphs describe renaming a function and defining a
chosen node. These two preparatory changes should be made,
independently of each other, prior to this patch. This patch should be
limited to moving code, with the subject line truncated to "move arch
independent code to drivers/of".
Just to be clear -
Split this patch into 3 parts as listed below:
PATCH #1: Rename remove_ima_buffer() to remove_ima_kexec_buffer()
PATCH #2: Define the chosen node
PATCH #3: Move the functions to drivers/of/fdt.c
From: Rob Herring <robh@kernel.org> Date: 2020-11-04 22:28:53
On Fri, Oct 30, 2020 at 10:44:26AM -0700, Lakshmi Ramasubramanian wrote:
The functions remove_ima_buffer() and delete_fdt_mem_rsv() that handle
carrying forward the IMA measurement logs on kexec for powerpc do not
have architecture specific code, but they are currently defined for
powerpc only.
remove_ima_buffer() and delete_fdt_mem_rsv() are used to remove
the IMA log entry from the device tree and free the memory reserved
for the log. These functions need to be defined even if the current
kernel does not support carrying forward IMA log across kexec since
the previous kernel could have supported that and therefore the current
kernel needs to free the allocation.
Rename remove_ima_buffer() to remove_ima_kexec_buffer().
Define remove_ima_kexec_buffer() and delete_fdt_mem_rsv() in
drivers/of/fdt.c. A later patch in this series will use these functions
to free the allocation, if any, made by the previous kernel for ARM64.
Define FDT_PROP_IMA_KEXEC_BUFFER for the chosen node, namely
"linux,ima-kexec-buffer", that is added to the DTB to hold
the address and the size of the memory reserved to carry
the IMA measurement log.
Co-developed-by: Prakhar Srivastava <redacted>
Signed-off-by: Prakhar Srivastava <redacted>
Signed-off-by: Lakshmi Ramasubramanian <redacted>
Reported-by: kernel test robot <redacted> error: kernel/kexec_file_fdt.c:30: undefined reference to `fdt_num_mem_rsv'
This should be added for a commit fixing the reported problem. 0-day
didn't report what this patch implements.
@@ -28,24 +30,6 @@ static int get_addr_size_cells(int *addr_cells, int *size_cells)return0;}-staticintdo_get_kexec_buffer(constvoid*prop,intlen,unsignedlong*addr,-size_t*size)-{-intret,addr_cells,size_cells;--ret=get_addr_size_cells(&addr_cells,&size_cells);-if(ret)-returnret;--if(len<4*(addr_cells+size_cells))-return-ENOENT;--*addr=of_read_number(prop,addr_cells);-*size=of_read_number(prop+4*addr_cells,size_cells);--return0;-}-/***ima_get_kexec_buffer-getIMAbufferfromthepreviouskernel*@addr:Onsuccessfulreturn,settopointtothebuffercontents.
@@ -100,37 +84,14 @@ int ima_free_kexec_buffer(void)}-/**-*remove_ima_buffer-removetheIMAbufferpropertyandreservationfrom@fdt-*-*TheIMAmeasurementbufferisofnousetoasubsequentkernel,sowealways-*removeitfromthedevicetree.-*/-voidremove_ima_buffer(void*fdt,intchosen_node)-{-intret,len;-unsignedlongaddr;-size_tsize;-constvoid*prop;--prop=fdt_getprop(fdt,chosen_node,"linux,ima-kexec-buffer",&len);-if(!prop)-return;--ret=do_get_kexec_buffer(prop,len,&addr,&size);-fdt_delprop(fdt,chosen_node,"linux,ima-kexec-buffer");-if(ret)-return;--ret=delete_fdt_mem_rsv(fdt,addr,size);-if(!ret)-pr_debug("Removed old IMA buffer reservation.\n");-}-#ifdef CONFIG_IMA_KEXEC/***arch_ima_add_kexec_buffer-doarch-specificstepstoaddtheIMAbuffer*+*@image:kimagestructtosetIMAbufferdata+*@load_addr:StartingaddresswhereIMAbufferisloadedat+*@size:NumberofbytesintheIMAbuffer+**ArchitecturesshouldusethisfunctiontopassontheIMAbuffer*informationtothenextkernel.*
@@ -179,7 +140,7 @@ int setup_ima_buffer(const struct kimage *image, void *fdt, int chosen_node)intret,addr_cells,size_cells,entry_size;u8value[16];-remove_ima_buffer(fdt,chosen_node);+remove_ima_kexec_buffer(fdt,chosen_node);if(!image->arch.ima_buffer_size)return0;
@@ -201,7 +162,7 @@ int setup_ima_buffer(const struct kimage *image, void *fdt, int chosen_node)if(ret)returnret;-ret=fdt_setprop(fdt,chosen_node,"linux,ima-kexec-buffer",value,+ret=fdt_setprop(fdt,chosen_node,FDT_PROP_IMA_KEXEC_BUFFER,value,entry_size);if(ret<0)return-EINVAL;
@@ -25,6 +25,7 @@#include<linux/serial_core.h>#include<linux/sysfs.h>#include<linux/random.h>+#include<linux/kexec.h>#include<asm/setup.h> /* for COMMAND_LINE_SIZE */#include<asm/page.h>
@@ -1289,4 +1290,113 @@ static int __init of_fdt_raw_init(void)late_initcall(of_fdt_raw_init);#endif+#ifdef CONFIG_HAVE_IMA_KEXEC
Can we avoid #ifdef and use IS_ENABLED() within the functions?
+/**
+ * do_get_kexec_buffer - Get address and size of IMA kexec buffer
+ *
+ * @prop: IMA kexec buffer node in the device tree
+ * @len: Size of the given device tree node property
+ * @addr: Return address of the node
+ * @size: Return size of the node
+ */
+int do_get_kexec_buffer(const void *prop, int len, unsigned long *addr,
+ size_t *size)
+{
+ int addr_cells, size_cells;
+ struct device_node *root;
+
+ root = of_find_node_by_path("/");
The code in fdt.c operates on flat trees. This is an unflattened tree.
There's nothing in this function specific to 'kexec buffer'.
This interface is kind of broken. 'prop' could come from anywhere in
the tree, but we always read the root address and size cells. Those only
apply to immediate child node properties. And anything other than
immediate root child nodes, there needs to be address translation.
+
+ return 0;
+}
+
+/**
+ * remove_ima_kexec_buffer - remove the IMA buffer property and
+ * reservation from @fdt
IIRC, kerneldoc requires this to be one line.
+ *
+ * @fdt: Flattened Device Tree to update
+ * @chosen_node: Offset to the chosen node in the device tree
+ *
+ * The IMA measurement buffer is of no use to a subsequent kernel,
+ * so we always remove it from the device tree.
+ */
+void remove_ima_kexec_buffer(void *fdt, int chosen_node)
+{
Can't this go in some common kexec code?
quoted hunk
+ int ret, len;
+ unsigned long addr;
+ size_t size;
+ const void *prop;
+
+ prop = fdt_getprop(fdt, chosen_node, FDT_PROP_IMA_KEXEC_BUFFER, &len);
+ if (!prop) {
+ pr_debug("Unable to find the ima kexec buffer node\n");
+ return;
+ }
+
+ ret = do_get_kexec_buffer(prop, len, &addr, &size);
+ fdt_delprop(fdt, chosen_node, FDT_PROP_IMA_KEXEC_BUFFER);
+ if (ret) {
+ pr_err("Unable to delete the ima kexec buffer node\n");
+ return;
+ }
+
+ ret = delete_fdt_mem_rsv(fdt, addr, size);
+ if (!ret)
+ pr_debug("Removed old IMA buffer reservation.\n");
+}
+#endif /* CONFIG_HAVE_IMA_KEXEC */
+
+#ifdef CONFIG_KEXEC_FILE
+/**
+ * delete_fdt_mem_rsv - delete memory reservation with given address and size
+ *
+ * @fdt: Flattened Device Tree to update
+ * @start: Starting address of the reservation to delete
+ * @size: Size of the reservation to delete
+ *
+ * Return: 0 on success, or negative errno on error.
+ */
+int delete_fdt_mem_rsv(void *fdt, unsigned long start, unsigned long size)
+{
+ int i, ret, num_rsvs = fdt_num_mem_rsv(fdt);
+
+ for (i = 0; i < num_rsvs; i++) {
+ uint64_t rsv_start, rsv_size;
+
+ ret = fdt_get_mem_rsv(fdt, i, &rsv_start, &rsv_size);
+ if (ret) {
+ pr_err("Malformed device tree.\n");
+ return -EINVAL;
+ }
+
+ if (rsv_start == start && rsv_size == size) {
+ ret = fdt_del_mem_rsv(fdt, i);
+ if (ret) {
+ pr_err("Error deleting device tree reservation.\n");
+ return -EINVAL;
+ }
+
+ pr_debug("Freed reserved memory at %lu of size %lu\n",
+ start, size);
+ return 0;
+ }
+ }
+
+ return -ENOENT;
+}
+#endif /* CONFIG_KEXEC_FILE */
+
#endif /* CONFIG_OF_EARLY_FLATTREE */
CONFIG_OF_EARLY_FLATTREE is wrong because that's all early boot (i.e.
init section) functions.
If these functions are implemented in fdt.c, then this is the wrong
header. But it's the implementation that should move.
quoted hunk
+extern void remove_ima_kexec_buffer(void *fdt, int chosen_node);
+extern int do_get_kexec_buffer(const void *prop, int len, unsigned long *addr,
+ size_t *size);
+#else
+static inline void remove_ima_kexec_buffer(void *fdt, int chosen_node) {}
+static inline int do_get_kexec_buffer(const void *prop, int len,
+ unsigned long *addr, size_t *size)
+{
+ return -EOPNOTSUPP;
+}
+#endif /* CONFIG_OF_EARLY_FLATTREE && CONFIG_HAVE_IMA_KEXEC */
+
+#if defined(CONFIG_OF_EARLY_FLATTREE) && defined(CONFIG_KEXEC_FILE)
+extern int delete_fdt_mem_rsv(void *fdt, unsigned long start,
+ unsigned long size);
+#else
+static inline int delete_fdt_mem_rsv(void *fdt, unsigned long start,
+ unsigned long size)
+{
+ return 0;
+}
+#endif /* CONFIG_OF_EARLY_FLATTREE && CONFIG_KEXEC_FILE */
+
#endif /* !defined(__ASSEBMLY__) */
#endif /* LINUX_KEXEC_H */
On 11/4/20 2:28 PM, Rob Herring wrote:
Hi Rob,
Thanks for reviewing the patch.
On Fri, Oct 30, 2020 at 10:44:26AM -0700, Lakshmi Ramasubramanian wrote:
quoted
The functions remove_ima_buffer() and delete_fdt_mem_rsv() that handle
carrying forward the IMA measurement logs on kexec for powerpc do not
have architecture specific code, but they are currently defined for
powerpc only.
remove_ima_buffer() and delete_fdt_mem_rsv() are used to remove
the IMA log entry from the device tree and free the memory reserved
for the log. These functions need to be defined even if the current
kernel does not support carrying forward IMA log across kexec since
the previous kernel could have supported that and therefore the current
kernel needs to free the allocation.
Rename remove_ima_buffer() to remove_ima_kexec_buffer().
Define remove_ima_kexec_buffer() and delete_fdt_mem_rsv() in
drivers/of/fdt.c. A later patch in this series will use these functions
to free the allocation, if any, made by the previous kernel for ARM64.
Define FDT_PROP_IMA_KEXEC_BUFFER for the chosen node, namely
"linux,ima-kexec-buffer", that is added to the DTB to hold
the address and the size of the memory reserved to carry
the IMA measurement log.
Co-developed-by: Prakhar Srivastava <redacted>
Signed-off-by: Prakhar Srivastava <redacted>
Signed-off-by: Lakshmi Ramasubramanian <redacted>
Reported-by: kernel test robot <redacted> error: kernel/kexec_file_fdt.c:30: undefined reference to `fdt_num_mem_rsv'
This should be added for a commit fixing the reported problem. 0-day
didn't report what this patch implements.
@@ -28,24 +30,6 @@ static int get_addr_size_cells(int *addr_cells, int *size_cells)return0;}-staticintdo_get_kexec_buffer(constvoid*prop,intlen,unsignedlong*addr,-size_t*size)-{-intret,addr_cells,size_cells;--ret=get_addr_size_cells(&addr_cells,&size_cells);-if(ret)-returnret;--if(len<4*(addr_cells+size_cells))-return-ENOENT;--*addr=of_read_number(prop,addr_cells);-*size=of_read_number(prop+4*addr_cells,size_cells);--return0;-}-/***ima_get_kexec_buffer-getIMAbufferfromthepreviouskernel*@addr:Onsuccessfulreturn,settopointtothebuffercontents.
@@ -100,37 +84,14 @@ int ima_free_kexec_buffer(void)}-/**-*remove_ima_buffer-removetheIMAbufferpropertyandreservationfrom@fdt-*-*TheIMAmeasurementbufferisofnousetoasubsequentkernel,sowealways-*removeitfromthedevicetree.-*/-voidremove_ima_buffer(void*fdt,intchosen_node)-{-intret,len;-unsignedlongaddr;-size_tsize;-constvoid*prop;--prop=fdt_getprop(fdt,chosen_node,"linux,ima-kexec-buffer",&len);-if(!prop)-return;--ret=do_get_kexec_buffer(prop,len,&addr,&size);-fdt_delprop(fdt,chosen_node,"linux,ima-kexec-buffer");-if(ret)-return;--ret=delete_fdt_mem_rsv(fdt,addr,size);-if(!ret)-pr_debug("Removed old IMA buffer reservation.\n");-}-#ifdef CONFIG_IMA_KEXEC/***arch_ima_add_kexec_buffer-doarch-specificstepstoaddtheIMAbuffer*+*@image:kimagestructtosetIMAbufferdata+*@load_addr:StartingaddresswhereIMAbufferisloadedat+*@size:NumberofbytesintheIMAbuffer+**ArchitecturesshouldusethisfunctiontopassontheIMAbuffer*informationtothenextkernel.*
@@ -179,7 +140,7 @@ int setup_ima_buffer(const struct kimage *image, void *fdt, int chosen_node)intret,addr_cells,size_cells,entry_size;u8value[16];-remove_ima_buffer(fdt,chosen_node);+remove_ima_kexec_buffer(fdt,chosen_node);if(!image->arch.ima_buffer_size)return0;
@@ -201,7 +162,7 @@ int setup_ima_buffer(const struct kimage *image, void *fdt, int chosen_node)if(ret)returnret;-ret=fdt_setprop(fdt,chosen_node,"linux,ima-kexec-buffer",value,+ret=fdt_setprop(fdt,chosen_node,FDT_PROP_IMA_KEXEC_BUFFER,value,entry_size);if(ret<0)return-EINVAL;
@@ -25,6 +25,7 @@#include<linux/serial_core.h>#include<linux/sysfs.h>#include<linux/random.h>+#include<linux/kexec.h>#include<asm/setup.h> /* for COMMAND_LINE_SIZE */#include<asm/page.h>
@@ -1289,4 +1290,113 @@ static int __init of_fdt_raw_init(void)late_initcall(of_fdt_raw_init);#endif+#ifdef CONFIG_HAVE_IMA_KEXEC
Can we avoid #ifdef and use IS_ENABLED() within the functions?
I can use IS_ENABLED() or move the functions to another C file and
conditionally build based on the CONFIG.
quoted
+/**
+ * do_get_kexec_buffer - Get address and size of IMA kexec buffer
+ *
+ * @prop: IMA kexec buffer node in the device tree
+ * @len: Size of the given device tree node property
+ * @addr: Return address of the node
+ * @size: Return size of the node
+ */
+int do_get_kexec_buffer(const void *prop, int len, unsigned long *addr,
+ size_t *size)
+{
+ int addr_cells, size_cells;
+ struct device_node *root;
+
+ root = of_find_node_by_path("/");
The code in fdt.c operates on flat trees. This is an unflattened tree.
Would it be better if I move these functions to a new C file under
"drivers/of"?
There's nothing in this function specific to 'kexec buffer'.
This interface is kind of broken. 'prop' could come from anywhere in
the tree, but we always read the root address and size cells. Those only
apply to immediate child node properties. And anything other than
immediate root child nodes, there needs to be address translation.
I moved this function from arch/powerpc/kexec/ima.c to here so that it
can be shared by ARM64 as well. Below is one of the usage of
do_get_kexec_buffer().
prop = of_get_property(of_chosen, "linux,ima-kexec-buffer", &len);
if (!prop)
return -ENOENT;
ret = do_get_kexec_buffer(prop, len, &tmp_addr, &tmp_size);
Is there a way to detect if the 'prop' is an immediate root child node
or not so that we can handle it appropriately in this interface function?
quoted
+
+ return 0;
+}
+
+/**
+ * remove_ima_kexec_buffer - remove the IMA buffer property and
+ * reservation from @fdt
IIRC, kerneldoc requires this to be one line.
I'll upate.
quoted
+ *
+ * @fdt: Flattened Device Tree to update
+ * @chosen_node: Offset to the chosen node in the device tree
+ *
+ * The IMA measurement buffer is of no use to a subsequent kernel,
+ * so we always remove it from the device tree.
+ */
+void remove_ima_kexec_buffer(void *fdt, int chosen_node)
+{
Can't this go in some common kexec code?
I'd considered moving this to "kernel", but Thiago suggested
"drivers/of" is a better place. If you have suggestions for a better
place, please let me know.
Note that this function needs to be available even when CONFIG_IMA is
not enabled. So I can't move it to "security/integrity/ima".
quoted
+ int ret, len;
+ unsigned long addr;
+ size_t size;
+ const void *prop;
+
+ prop = fdt_getprop(fdt, chosen_node, FDT_PROP_IMA_KEXEC_BUFFER, &len);
+ if (!prop) {
+ pr_debug("Unable to find the ima kexec buffer node\n");
+ return;
+ }
+
+ ret = do_get_kexec_buffer(prop, len, &addr, &size);
+ fdt_delprop(fdt, chosen_node, FDT_PROP_IMA_KEXEC_BUFFER);
+ if (ret) {
+ pr_err("Unable to delete the ima kexec buffer node\n");
+ return;
+ }
+
+ ret = delete_fdt_mem_rsv(fdt, addr, size);
+ if (!ret)
+ pr_debug("Removed old IMA buffer reservation.\n");
+}
+#endif /* CONFIG_HAVE_IMA_KEXEC */
+
+#ifdef CONFIG_KEXEC_FILE
+/**
+ * delete_fdt_mem_rsv - delete memory reservation with given address and size
+ *
+ * @fdt: Flattened Device Tree to update
+ * @start: Starting address of the reservation to delete
+ * @size: Size of the reservation to delete
+ *
+ * Return: 0 on success, or negative errno on error.
+ */
+int delete_fdt_mem_rsv(void *fdt, unsigned long start, unsigned long size)
+{
+ int i, ret, num_rsvs = fdt_num_mem_rsv(fdt);
+
+ for (i = 0; i < num_rsvs; i++) {
+ uint64_t rsv_start, rsv_size;
+
+ ret = fdt_get_mem_rsv(fdt, i, &rsv_start, &rsv_size);
+ if (ret) {
+ pr_err("Malformed device tree.\n");
+ return -EINVAL;
+ }
+
+ if (rsv_start == start && rsv_size == size) {
+ ret = fdt_del_mem_rsv(fdt, i);
+ if (ret) {
+ pr_err("Error deleting device tree reservation.\n");
+ return -EINVAL;
+ }
+
+ pr_debug("Freed reserved memory at %lu of size %lu\n",
+ start, size);
+ return 0;
+ }
+ }
+
+ return -ENOENT;
+}
+#endif /* CONFIG_KEXEC_FILE */
+
#endif /* CONFIG_OF_EARLY_FLATTREE */
CONFIG_OF_EARLY_FLATTREE is wrong because that's all early boot (i.e.
init section) functions.
If these functions are implemented in fdt.c, then this is the wrong
header. But it's the implementation that should move.
If you think defining these functions in "drivers/of" is okay, I'll move
them to a new C file in OF.
Would CONFIG_OF_FLATTREE be a better one to enable these ima kexec
functions? "of_" and "fdt_" are the functions called by these ima kexec
functions.
quoted
+extern void remove_ima_kexec_buffer(void *fdt, int chosen_node);
+extern int do_get_kexec_buffer(const void *prop, int len, unsigned long *addr,
+ size_t *size);
+#else
+static inline void remove_ima_kexec_buffer(void *fdt, int chosen_node) {}
+static inline int do_get_kexec_buffer(const void *prop, int len,
+ unsigned long *addr, size_t *size)
+{
+ return -EOPNOTSUPP;
+}
+#endif /* CONFIG_OF_EARLY_FLATTREE && CONFIG_HAVE_IMA_KEXEC */
+
+#if defined(CONFIG_OF_EARLY_FLATTREE) && defined(CONFIG_KEXEC_FILE)
+extern int delete_fdt_mem_rsv(void *fdt, unsigned long start,
+ unsigned long size);
+#else
+static inline int delete_fdt_mem_rsv(void *fdt, unsigned long start,
+ unsigned long size)
+{
+ return 0;
+}
+#endif /* CONFIG_OF_EARLY_FLATTREE && CONFIG_KEXEC_FILE */
+
#endif /* !defined(__ASSEBMLY__) */
#endif /* LINUX_KEXEC_H */
From: Rob Herring <robh@kernel.org> Date: 2020-11-05 14:39:14
On Wed, Nov 4, 2020 at 6:46 PM Lakshmi Ramasubramanian
[off-list ref] wrote:
On 11/4/20 2:28 PM, Rob Herring wrote:
Hi Rob,
Thanks for reviewing the patch.
quoted
On Fri, Oct 30, 2020 at 10:44:26AM -0700, Lakshmi Ramasubramanian wrote:
quoted
The functions remove_ima_buffer() and delete_fdt_mem_rsv() that handle
carrying forward the IMA measurement logs on kexec for powerpc do not
have architecture specific code, but they are currently defined for
powerpc only.
remove_ima_buffer() and delete_fdt_mem_rsv() are used to remove
the IMA log entry from the device tree and free the memory reserved
for the log. These functions need to be defined even if the current
kernel does not support carrying forward IMA log across kexec since
the previous kernel could have supported that and therefore the current
kernel needs to free the allocation.
Rename remove_ima_buffer() to remove_ima_kexec_buffer().
Define remove_ima_kexec_buffer() and delete_fdt_mem_rsv() in
drivers/of/fdt.c. A later patch in this series will use these functions
to free the allocation, if any, made by the previous kernel for ARM64.
Define FDT_PROP_IMA_KEXEC_BUFFER for the chosen node, namely
"linux,ima-kexec-buffer", that is added to the DTB to hold
the address and the size of the memory reserved to carry
the IMA measurement log.
Co-developed-by: Prakhar Srivastava <redacted>
Signed-off-by: Prakhar Srivastava <redacted>
Signed-off-by: Lakshmi Ramasubramanian <redacted>
Reported-by: kernel test robot <redacted> error: kernel/kexec_file_fdt.c:30: undefined reference to `fdt_num_mem_rsv'
This should be added for a commit fixing the reported problem. 0-day
didn't report what this patch implements.
@@ -28,24 +30,6 @@ static int get_addr_size_cells(int *addr_cells, int *size_cells)return0;}-staticintdo_get_kexec_buffer(constvoid*prop,intlen,unsignedlong*addr,-size_t*size)-{-intret,addr_cells,size_cells;--ret=get_addr_size_cells(&addr_cells,&size_cells);-if(ret)-returnret;--if(len<4*(addr_cells+size_cells))-return-ENOENT;--*addr=of_read_number(prop,addr_cells);-*size=of_read_number(prop+4*addr_cells,size_cells);--return0;-}-/***ima_get_kexec_buffer-getIMAbufferfromthepreviouskernel*@addr:Onsuccessfulreturn,settopointtothebuffercontents.
@@ -100,37 +84,14 @@ int ima_free_kexec_buffer(void)}-/**-*remove_ima_buffer-removetheIMAbufferpropertyandreservationfrom@fdt-*-*TheIMAmeasurementbufferisofnousetoasubsequentkernel,sowealways-*removeitfromthedevicetree.-*/-voidremove_ima_buffer(void*fdt,intchosen_node)-{-intret,len;-unsignedlongaddr;-size_tsize;-constvoid*prop;--prop=fdt_getprop(fdt,chosen_node,"linux,ima-kexec-buffer",&len);-if(!prop)-return;--ret=do_get_kexec_buffer(prop,len,&addr,&size);-fdt_delprop(fdt,chosen_node,"linux,ima-kexec-buffer");-if(ret)-return;--ret=delete_fdt_mem_rsv(fdt,addr,size);-if(!ret)-pr_debug("Removed old IMA buffer reservation.\n");-}-#ifdef CONFIG_IMA_KEXEC/***arch_ima_add_kexec_buffer-doarch-specificstepstoaddtheIMAbuffer*+*@image:kimagestructtosetIMAbufferdata+*@load_addr:StartingaddresswhereIMAbufferisloadedat+*@size:NumberofbytesintheIMAbuffer+**ArchitecturesshouldusethisfunctiontopassontheIMAbuffer*informationtothenextkernel.*
@@ -179,7 +140,7 @@ int setup_ima_buffer(const struct kimage *image, void *fdt, int chosen_node)intret,addr_cells,size_cells,entry_size;u8value[16];-remove_ima_buffer(fdt,chosen_node);+remove_ima_kexec_buffer(fdt,chosen_node);if(!image->arch.ima_buffer_size)return0;
@@ -201,7 +162,7 @@ int setup_ima_buffer(const struct kimage *image, void *fdt, int chosen_node)if(ret)returnret;-ret=fdt_setprop(fdt,chosen_node,"linux,ima-kexec-buffer",value,+ret=fdt_setprop(fdt,chosen_node,FDT_PROP_IMA_KEXEC_BUFFER,value,entry_size);if(ret<0)return-EINVAL;
@@ -25,6 +25,7 @@#include<linux/serial_core.h>#include<linux/sysfs.h>#include<linux/random.h>+#include<linux/kexec.h>#include<asm/setup.h> /* for COMMAND_LINE_SIZE */#include<asm/page.h>
@@ -1289,4 +1290,113 @@ static int __init of_fdt_raw_init(void)late_initcall(of_fdt_raw_init);#endif+#ifdef CONFIG_HAVE_IMA_KEXEC
Can we avoid #ifdef and use IS_ENABLED() within the functions?
I can use IS_ENABLED() or move the functions to another C file and
conditionally build based on the CONFIG.
quoted
quoted
+/**
+ * do_get_kexec_buffer - Get address and size of IMA kexec buffer
+ *
+ * @prop: IMA kexec buffer node in the device tree
+ * @len: Size of the given device tree node property
+ * @addr: Return address of the node
+ * @size: Return size of the node
+ */
+int do_get_kexec_buffer(const void *prop, int len, unsigned long *addr,
+ size_t *size)
+{
+ int addr_cells, size_cells;
+ struct device_node *root;
+
+ root = of_find_node_by_path("/");
The code in fdt.c operates on flat trees. This is an unflattened tree.
Would it be better if I move these functions to a new C file under
"drivers/of"?
There's nothing in this function specific to 'kexec buffer'.
This interface is kind of broken. 'prop' could come from anywhere in
the tree, but we always read the root address and size cells. Those only
apply to immediate child node properties. And anything other than
immediate root child nodes, there needs to be address translation.
I moved this function from arch/powerpc/kexec/ima.c to here so that it
can be shared by ARM64 as well. Below is one of the usage of
do_get_kexec_buffer().
prop = of_get_property(of_chosen, "linux,ima-kexec-buffer", &len);
if (!prop)
return -ENOENT;
ret = do_get_kexec_buffer(prop, len, &tmp_addr, &tmp_size);
Is there a way to detect if the 'prop' is an immediate root child node
or not so that we can handle it appropriately in this interface function?
Just don't split up the function.
quoted
quoted
+
+ return 0;
+}
+
+/**
+ * remove_ima_kexec_buffer - remove the IMA buffer property and
+ * reservation from @fdt
IIRC, kerneldoc requires this to be one line.
I'll upate.
quoted
quoted
+ *
+ * @fdt: Flattened Device Tree to update
+ * @chosen_node: Offset to the chosen node in the device tree
+ *
+ * The IMA measurement buffer is of no use to a subsequent kernel,
+ * so we always remove it from the device tree.
+ */
+void remove_ima_kexec_buffer(void *fdt, int chosen_node)
+{
Can't this go in some common kexec code?
I'd considered moving this to "kernel", but Thiago suggested
"drivers/of" is a better place. If you have suggestions for a better
place, please let me know.
Humm, I guess drivers/of/ is fine, but it should be its own file.
Also, there's nothing arch specific about handling bootargs, initrd,
etc., so create a common function to handle all that. You can probably
include allocating and copying the new fdt as part of that. Powerpc
does kmalloc and arm64 does vmalloc for the new fdt. Is that a
necessary difference?
Then the IMA handling can all be private to the new file?
Note that this function needs to be available even when CONFIG_IMA is
not enabled. So I can't move it to "security/integrity/ima".
quoted
quoted
+ int ret, len;
+ unsigned long addr;
+ size_t size;
+ const void *prop;
+
+ prop = fdt_getprop(fdt, chosen_node, FDT_PROP_IMA_KEXEC_BUFFER, &len);
+ if (!prop) {
+ pr_debug("Unable to find the ima kexec buffer node\n");
+ return;
+ }
+
+ ret = do_get_kexec_buffer(prop, len, &addr, &size);
+ fdt_delprop(fdt, chosen_node, FDT_PROP_IMA_KEXEC_BUFFER);
+ if (ret) {
+ pr_err("Unable to delete the ima kexec buffer node\n");
+ return;
+ }
+
+ ret = delete_fdt_mem_rsv(fdt, addr, size);
+ if (!ret)
+ pr_debug("Removed old IMA buffer reservation.\n");
+}
+#endif /* CONFIG_HAVE_IMA_KEXEC */
+
+#ifdef CONFIG_KEXEC_FILE
+/**
+ * delete_fdt_mem_rsv - delete memory reservation with given address and size
+ *
+ * @fdt: Flattened Device Tree to update
+ * @start: Starting address of the reservation to delete
+ * @size: Size of the reservation to delete
+ *
+ * Return: 0 on success, or negative errno on error.
+ */
+int delete_fdt_mem_rsv(void *fdt, unsigned long start, unsigned long size)
+{
+ int i, ret, num_rsvs = fdt_num_mem_rsv(fdt);
+
+ for (i = 0; i < num_rsvs; i++) {
+ uint64_t rsv_start, rsv_size;
+
+ ret = fdt_get_mem_rsv(fdt, i, &rsv_start, &rsv_size);
+ if (ret) {
+ pr_err("Malformed device tree.\n");
+ return -EINVAL;
+ }
+
+ if (rsv_start == start && rsv_size == size) {
+ ret = fdt_del_mem_rsv(fdt, i);
+ if (ret) {
+ pr_err("Error deleting device tree reservation.\n");
+ return -EINVAL;
+ }
+
+ pr_debug("Freed reserved memory at %lu of size %lu\n",
+ start, size);
+ return 0;
+ }
+ }
+
+ return -ENOENT;
+}
+#endif /* CONFIG_KEXEC_FILE */
+
#endif /* CONFIG_OF_EARLY_FLATTREE */
CONFIG_OF_EARLY_FLATTREE is wrong because that's all early boot (i.e.
init section) functions.
If these functions are implemented in fdt.c, then this is the wrong
header. But it's the implementation that should move.
If you think defining these functions in "drivers/of" is okay, I'll move
them to a new C file in OF.
Would CONFIG_OF_FLATTREE be a better one to enable these ima kexec
functions? "of_" and "fdt_" are the functions called by these ima kexec
functions.
Yes.
quoted
quoted
+extern void remove_ima_kexec_buffer(void *fdt, int chosen_node);
+extern int do_get_kexec_buffer(const void *prop, int len, unsigned long *addr,
+ size_t *size);
+#else
+static inline void remove_ima_kexec_buffer(void *fdt, int chosen_node) {}
+static inline int do_get_kexec_buffer(const void *prop, int len,
+ unsigned long *addr, size_t *size)
+{
+ return -EOPNOTSUPP;
+}
+#endif /* CONFIG_OF_EARLY_FLATTREE && CONFIG_HAVE_IMA_KEXEC */
+
+#if defined(CONFIG_OF_EARLY_FLATTREE) && defined(CONFIG_KEXEC_FILE)
+extern int delete_fdt_mem_rsv(void *fdt, unsigned long start,
+ unsigned long size);
+#else
+static inline int delete_fdt_mem_rsv(void *fdt, unsigned long start,
+ unsigned long size)
+{
+ return 0;
+}
+#endif /* CONFIG_OF_EARLY_FLATTREE && CONFIG_KEXEC_FILE */
+
#endif /* !defined(__ASSEBMLY__) */
#endif /* LINUX_KEXEC_H */
On Wed, Nov 4, 2020 at 6:46 PM Lakshmi Ramasubramanian
[off-list ref] wrote:
quoted
On 11/4/20 2:28 PM, Rob Herring wrote:
Hi Rob,
Thanks for reviewing the patch.
quoted
On Fri, Oct 30, 2020 at 10:44:26AM -0700, Lakshmi Ramasubramanian wrote:
quoted
The functions remove_ima_buffer() and delete_fdt_mem_rsv() that handle
carrying forward the IMA measurement logs on kexec for powerpc do not
have architecture specific code, but they are currently defined for
powerpc only.
remove_ima_buffer() and delete_fdt_mem_rsv() are used to remove
the IMA log entry from the device tree and free the memory reserved
for the log. These functions need to be defined even if the current
kernel does not support carrying forward IMA log across kexec since
the previous kernel could have supported that and therefore the current
kernel needs to free the allocation.
Rename remove_ima_buffer() to remove_ima_kexec_buffer().
Define remove_ima_kexec_buffer() and delete_fdt_mem_rsv() in
drivers/of/fdt.c. A later patch in this series will use these functions
to free the allocation, if any, made by the previous kernel for ARM64.
Define FDT_PROP_IMA_KEXEC_BUFFER for the chosen node, namely
"linux,ima-kexec-buffer", that is added to the DTB to hold
the address and the size of the memory reserved to carry
the IMA measurement log.
Co-developed-by: Prakhar Srivastava <redacted>
Signed-off-by: Prakhar Srivastava <redacted>
Signed-off-by: Lakshmi Ramasubramanian <redacted>
Reported-by: kernel test robot <redacted> error: kernel/kexec_file_fdt.c:30: undefined reference to `fdt_num_mem_rsv'
This should be added for a commit fixing the reported problem. 0-day
didn't report what this patch implements.
@@ -28,24 +30,6 @@ static int get_addr_size_cells(int *addr_cells, int *size_cells)return0;}-staticintdo_get_kexec_buffer(constvoid*prop,intlen,unsignedlong*addr,-size_t*size)-{-intret,addr_cells,size_cells;--ret=get_addr_size_cells(&addr_cells,&size_cells);-if(ret)-returnret;--if(len<4*(addr_cells+size_cells))-return-ENOENT;--*addr=of_read_number(prop,addr_cells);-*size=of_read_number(prop+4*addr_cells,size_cells);--return0;-}-/***ima_get_kexec_buffer-getIMAbufferfromthepreviouskernel*@addr:Onsuccessfulreturn,settopointtothebuffercontents.
@@ -100,37 +84,14 @@ int ima_free_kexec_buffer(void)}-/**-*remove_ima_buffer-removetheIMAbufferpropertyandreservationfrom@fdt-*-*TheIMAmeasurementbufferisofnousetoasubsequentkernel,sowealways-*removeitfromthedevicetree.-*/-voidremove_ima_buffer(void*fdt,intchosen_node)-{-intret,len;-unsignedlongaddr;-size_tsize;-constvoid*prop;--prop=fdt_getprop(fdt,chosen_node,"linux,ima-kexec-buffer",&len);-if(!prop)-return;--ret=do_get_kexec_buffer(prop,len,&addr,&size);-fdt_delprop(fdt,chosen_node,"linux,ima-kexec-buffer");-if(ret)-return;--ret=delete_fdt_mem_rsv(fdt,addr,size);-if(!ret)-pr_debug("Removed old IMA buffer reservation.\n");-}-#ifdef CONFIG_IMA_KEXEC/***arch_ima_add_kexec_buffer-doarch-specificstepstoaddtheIMAbuffer*+*@image:kimagestructtosetIMAbufferdata+*@load_addr:StartingaddresswhereIMAbufferisloadedat+*@size:NumberofbytesintheIMAbuffer+**ArchitecturesshouldusethisfunctiontopassontheIMAbuffer*informationtothenextkernel.*
@@ -179,7 +140,7 @@ int setup_ima_buffer(const struct kimage *image, void *fdt, int chosen_node)intret,addr_cells,size_cells,entry_size;u8value[16];-remove_ima_buffer(fdt,chosen_node);+remove_ima_kexec_buffer(fdt,chosen_node);if(!image->arch.ima_buffer_size)return0;
@@ -201,7 +162,7 @@ int setup_ima_buffer(const struct kimage *image, void *fdt, int chosen_node)if(ret)returnret;-ret=fdt_setprop(fdt,chosen_node,"linux,ima-kexec-buffer",value,+ret=fdt_setprop(fdt,chosen_node,FDT_PROP_IMA_KEXEC_BUFFER,value,entry_size);if(ret<0)return-EINVAL;
@@ -25,6 +25,7 @@#include<linux/serial_core.h>#include<linux/sysfs.h>#include<linux/random.h>+#include<linux/kexec.h>#include<asm/setup.h> /* for COMMAND_LINE_SIZE */#include<asm/page.h>
@@ -1289,4 +1290,113 @@ static int __init of_fdt_raw_init(void)late_initcall(of_fdt_raw_init);#endif+#ifdef CONFIG_HAVE_IMA_KEXEC
Can we avoid #ifdef and use IS_ENABLED() within the functions?
I can use IS_ENABLED() or move the functions to another C file and
conditionally build based on the CONFIG.
quoted
quoted
+/**
+ * do_get_kexec_buffer - Get address and size of IMA kexec buffer
+ *
+ * @prop: IMA kexec buffer node in the device tree
+ * @len: Size of the given device tree node property
+ * @addr: Return address of the node
+ * @size: Return size of the node
+ */
+int do_get_kexec_buffer(const void *prop, int len, unsigned long *addr,
+ size_t *size)
+{
+ int addr_cells, size_cells;
+ struct device_node *root;
+
+ root = of_find_node_by_path("/");
The code in fdt.c operates on flat trees. This is an unflattened tree.
Would it be better if I move these functions to a new C file under
"drivers/of"?
There's nothing in this function specific to 'kexec buffer'.
This interface is kind of broken. 'prop' could come from anywhere in
the tree, but we always read the root address and size cells. Those only
apply to immediate child node properties. And anything other than
immediate root child nodes, there needs to be address translation.
I moved this function from arch/powerpc/kexec/ima.c to here so that it
can be shared by ARM64 as well. Below is one of the usage of
do_get_kexec_buffer().
prop = of_get_property(of_chosen, "linux,ima-kexec-buffer", &len);
if (!prop)
return -ENOENT;
ret = do_get_kexec_buffer(prop, len, &tmp_addr, &tmp_size);
Is there a way to detect if the 'prop' is an immediate root child node
or not so that we can handle it appropriately in this interface function?
Just don't split up the function.
ok
quoted
quoted
quoted
+
+ return 0;
+}
+
+/**
+ * remove_ima_kexec_buffer - remove the IMA buffer property and
+ * reservation from @fdt
IIRC, kerneldoc requires this to be one line.
I'll upate.
quoted
quoted
+ *
+ * @fdt: Flattened Device Tree to update
+ * @chosen_node: Offset to the chosen node in the device tree
+ *
+ * The IMA measurement buffer is of no use to a subsequent kernel,
+ * so we always remove it from the device tree.
+ */
+void remove_ima_kexec_buffer(void *fdt, int chosen_node)
+{
Can't this go in some common kexec code?
I'd considered moving this to "kernel", but Thiago suggested
"drivers/of" is a better place. If you have suggestions for a better
place, please let me know.
Humm, I guess drivers/of/ is fine, but it should be its own file.
Also, there's nothing arch specific about handling bootargs, initrd,
etc., so create a common function to handle all that. You can probably
include allocating and copying the new fdt as part of that. Powerpc
does kmalloc and arm64 does vmalloc for the new fdt. Is that a
necessary difference?
Agreed - I also think there's nothing arch specific about handling
bootargs, initrd, etc. But refactoring the code that handles the above
would be a much bigger change.
Would it be fine if we do it in two or more steps (to minimize
regression risks)?
#1 - move minimal functions/code to add support for ima buffer on
kexec for ARM64 (addressed in this patch series)
#2+ - refactor further to move more arch independent code to common
functions in the next set of patche series.
Then the IMA handling can all be private to the new file?
quoted
Note that this function needs to be available even when CONFIG_IMA is
not enabled. So I can't move it to "security/integrity/ima".
quoted
quoted
+ int ret, len;
+ unsigned long addr;
+ size_t size;
+ const void *prop;
+
+ prop = fdt_getprop(fdt, chosen_node, FDT_PROP_IMA_KEXEC_BUFFER, &len);
+ if (!prop) {
+ pr_debug("Unable to find the ima kexec buffer node\n");
+ return;
+ }
+
+ ret = do_get_kexec_buffer(prop, len, &addr, &size);
+ fdt_delprop(fdt, chosen_node, FDT_PROP_IMA_KEXEC_BUFFER);
+ if (ret) {
+ pr_err("Unable to delete the ima kexec buffer node\n");
+ return;
+ }
+
+ ret = delete_fdt_mem_rsv(fdt, addr, size);
+ if (!ret)
+ pr_debug("Removed old IMA buffer reservation.\n");
+}
+#endif /* CONFIG_HAVE_IMA_KEXEC */
+
+#ifdef CONFIG_KEXEC_FILE
+/**
+ * delete_fdt_mem_rsv - delete memory reservation with given address and size
+ *
+ * @fdt: Flattened Device Tree to update
+ * @start: Starting address of the reservation to delete
+ * @size: Size of the reservation to delete
+ *
+ * Return: 0 on success, or negative errno on error.
+ */
+int delete_fdt_mem_rsv(void *fdt, unsigned long start, unsigned long size)
+{
+ int i, ret, num_rsvs = fdt_num_mem_rsv(fdt);
+
+ for (i = 0; i < num_rsvs; i++) {
+ uint64_t rsv_start, rsv_size;
+
+ ret = fdt_get_mem_rsv(fdt, i, &rsv_start, &rsv_size);
+ if (ret) {
+ pr_err("Malformed device tree.\n");
+ return -EINVAL;
+ }
+
+ if (rsv_start == start && rsv_size == size) {
+ ret = fdt_del_mem_rsv(fdt, i);
+ if (ret) {
+ pr_err("Error deleting device tree reservation.\n");
+ return -EINVAL;
+ }
+
+ pr_debug("Freed reserved memory at %lu of size %lu\n",
+ start, size);
+ return 0;
+ }
+ }
+
+ return -ENOENT;
+}
+#endif /* CONFIG_KEXEC_FILE */
+
#endif /* CONFIG_OF_EARLY_FLATTREE */
CONFIG_OF_EARLY_FLATTREE is wrong because that's all early boot (i.e.
init section) functions.
If these functions are implemented in fdt.c, then this is the wrong
header. But it's the implementation that should move.
If you think defining these functions in "drivers/of" is okay, I'll move
them to a new C file in OF.
Would CONFIG_OF_FLATTREE be a better one to enable these ima kexec
functions? "of_" and "fdt_" are the functions called by these ima kexec
functions.
Yes.
Thanks - I will use CONFIG_OF_FLATTREE to handle this change.
quoted
quoted
quoted
+extern void remove_ima_kexec_buffer(void *fdt, int chosen_node);
+extern int do_get_kexec_buffer(const void *prop, int len, unsigned long *addr,
+ size_t *size);
+#else
+static inline void remove_ima_kexec_buffer(void *fdt, int chosen_node) {}
+static inline int do_get_kexec_buffer(const void *prop, int len,
+ unsigned long *addr, size_t *size)
+{
+ return -EOPNOTSUPP;
+}
+#endif /* CONFIG_OF_EARLY_FLATTREE && CONFIG_HAVE_IMA_KEXEC */
+
+#if defined(CONFIG_OF_EARLY_FLATTREE) && defined(CONFIG_KEXEC_FILE)
+extern int delete_fdt_mem_rsv(void *fdt, unsigned long start,
+ unsigned long size);
+#else
+static inline int delete_fdt_mem_rsv(void *fdt, unsigned long start,
+ unsigned long size)
+{
+ return 0;
+}
+#endif /* CONFIG_OF_EARLY_FLATTREE && CONFIG_KEXEC_FILE */
+
#endif /* !defined(__ASSEBMLY__) */
#endif /* LINUX_KEXEC_H */