arm: mach-keystone: Use appended original image size in image processing
PATCH v2 1/1 arm: mach-keystone: Use appended original image size in image processing
When an image is signed/encrypted on K2 devices the image may get padded to meet alignment requirements for the signature/encryption type. The original size is appended as 4 bytes little-endian to the end of the final image.
Normally the trailing extra bytes are ignored and so restoring the exact original size is not important. In the case of initrd the original size is important as the kernel uses it to look for additional filesystem data and can do the wrong thing when the size is not correct.
Read off the original size and report it back from the image post processing stage.
---
Changes from v1:
- Use get_unaligned_le32
- Fixup header/copyright while here
arch/arm/mach-keystone/mon.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
arch/arm/mach-keystone/mon.c +5 -5
@@ -1,11 +1,11 @@// SPDX-License-Identifier: GPL-2.0+ /* -* K2HK: secure kernel command file +* K2x: Secure commands file * -* (C) Copyright 2012-2014 -* Texas Instruments Incorporated, <www.ti.com> +* Copyright (C) 2012-2019 Texas Instruments Incorporated - http://www.ti.com/ */ +#include <asm/unaligned.h> #include <common.h> #include <command.h> #include <mach/mon.h>
@@ -120,9 +120,9 @@ void board_fit_image_post_process(void **p_image, size_t *p_size)/* * Overwrite the image headers after authentication * and decryption. Update size to reflect removal -* of header. +* of header and restore original file size. */ - *p_size -=KS2_HS_SEC_HEADER_LEN ; + *p_size =get_unaligned_le32 (image + (*p_size -4 ));memcpy (image, image +KS2_HS_SEC_HEADER_LEN , *p_size);/*
Signature · 1 line
2.17.1
PATCH v2 1/1 arm: mach-keystone: Use appended original image size in image processing
Quoted 11 lines · Andrew F. Davis
When an image is signed/encrypted on K2 devices the image may get padded to meet alignment requirements for the signature/encryption type. The original size is appended as 4 bytes little-endian to the end of the final image.
Normally the trailing extra bytes are ignored and so restoring the exact original size is not important. In the case of initrd the original size is important as the kernel uses it to look for additional filesystem data and can do the wrong thing when the size is not correct.
Quoted 4 lines
Read off the original size and report it back from the image post processing stage.
Signed-off-by Andrew F. Davis <[email protected]>
Thanks and regards,
Lokesh
PATCH v2 1/1 arm: mach-keystone: Use appended original image size in image processing
In reply to Andrew F. DavisQuoted 11 lines · Andrew F. Davis
When an image is signed/encrypted on K2 devices the image may get padded to meet alignment requirements for the signature/encryption type. The original size is appended as 4 bytes little-endian to the end of the final image.
Normally the trailing extra bytes are ignored and so restoring the exact original size is not important. In the case of initrd the original size is important as the kernel uses it to look for additional filesystem data and can do the wrong thing when the size is not correct.
Quoted 5 lines
Read off the original size and report it back from the image post processing stage.
Signed-off-by Andrew F. Davis <[email protected]>Reviewed-by Lokesh Vutla <[email protected]>
Applied to u-boot/master, thanks!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190729/039ba877/attachment.sig>