[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] device-tree/kernel: Use memcpy in output_length()


  • To: Jason Andryuk <jason.andryuk@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
  • From: "Orzel, Michal" <michal.orzel@xxxxxxx>
  • Date: Wed, 23 Jul 2025 08:33:59 +0200
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=amd.com; dmarc=pass action=none header.from=amd.com; dkim=pass header.d=amd.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=OhicKrzQgET9gN/R8TtOW6GJKJPWejtMzYorzdFeOXA=; b=XI+hlCYgMNkCSVtMYP8qFxeiaYnRuXURfEQ0rgnQ/z9YhpS7mLHwhiagCo/i9nkBFD5Jq6kxm8BMFAw9YWJL7PgV1Joysc8CUko56T53H+TQ+h+o9x8rsHjb1w+chn4XIsmnOZWL4x+hklIzU2zOtx7J9P7eLqu7UAhzgStQ+w0yCZsZs8aw91YztnyDmLRTAOSyW0ocHXxdIre6w44VWJ7PNdp7McDG+l48RCNWMTiPKH2WX2BybQchf1BQZDYLlTnCmtJQOGKXkAUQTs6CuZ5JQ/GY0Hqo3AyigjMtRWb6HQFQOIShgSjGsVW24R8t6+YNiqSWbexHOGN41MZg2g==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=GCDBVI5ciFYcd/RFPZNNKrY+Fa+epQ9Z1dglCsXWJK8eLnI7usWlp7AVpHxhlbIxmJ7j8PB9vnRJzbTIvfLeo6s7vCtUxOyI5PXZOASwQDfzHCRgUu6GMGVTZK2tbEmKBGrlAD1fMn8eJSJe/Xz6r/dWY1LGI002tYtgyy1i6f4fYlIqWJi94D7esVaHTQYCRx2pbHSnhoUDW8nSrOloHprfGTNImXNB9GP3ObV67z0DU84J4uLU3OZViiiuoqNnWQxBDFQdWXlqhCnfYa5Rj8n9KRUfAxRl9KzSzDj6M+QhVw2ahINpR8XtOOW1V0IqfRyXcUIYkzLyI5sWa3bU2Q==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=amd.com;
  • Cc: Stefano Stabellini <sstabellini@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, Bertrand Marquis <bertrand.marquis@xxxxxxx>
  • Delivery-date: Wed, 23 Jul 2025 06:34:17 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>


On 22/07/2025 06:50, Jason Andryuk wrote:
> On 2025-07-22 03:46, Michal Orzel wrote:
>> Trying to boot a compressed kernel with UBSAN enabled, results in the
>> following warning:
>> (XEN) UBSAN: Undefined behaviour in common/device-tree/kernel.c:21:12
>> (XEN) load of misaligned address 00000a0040f89867 for type 'uint32_t'
>> (XEN) which requires 4 byte alignment
>> ...
>> (XEN)    [<00000a0000529964>] kernel_decompress+0x2bc/0x5bc
>> (XEN)    [<00000a000052a354>] kernel_probe+0x6f0/0x734
>> (XEN)    [<00000a0000528714>] dom0less-build.c#construct_domU+0x188/0x9d8
>>
>> If &image[image_len - 4] is not aligned to 4B boundary it causes
>> unaligned access which is undefined behavior on Arm. Use memcpy instead
>> to be safe.
>>
>> Fixes: c1be0b102e0e ("xen/arm: support gzip compressed kernels")
>> Signed-off-by: Michal Orzel <michal.orzel@xxxxxxx>
>> ---
>>   xen/common/device-tree/kernel.c | 6 +++++-
>>   1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/xen/common/device-tree/kernel.c 
>> b/xen/common/device-tree/kernel.c
>> index ef393182b691..28096121a52d 100644
>> --- a/xen/common/device-tree/kernel.c
>> +++ b/xen/common/device-tree/kernel.c
>> @@ -18,7 +18,11 @@
>>   
>>   static uint32_t __init output_length(char *image, unsigned long image_len)
>>   {
>> -    return *(uint32_t *)&image[image_len - 4];
> 
> Maybe just:
>      return get_unaligned_le32(&image[image_len - 4]);
> 
> You'll also need:
> #include <xen/unaligned.h>
> 
> The gzip size is little endian, 
I thought about this solution but decided to use memcpy because one day we may
want to support other compression algorithms and forcing LE could cause issues.

I'm ok either way. Let other maintainers decide.

~Michal




 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.