NetBSD Problem Report #58364

From www@netbsd.org  Tue Jun 25 00:04:15 2024
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 528CD1A923A
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 25 Jun 2024 00:04:15 +0000 (UTC)
Message-Id: <20240625000413.F0EF51A923C@mollari.NetBSD.org>
Date: Tue, 25 Jun 2024 00:04:13 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: x86 kernels have nearly two megabytes of zero padding at the start
X-Send-Pr-Version: www-1.0

>Number:         58364
>Category:       port-amd64
>Synopsis:       x86 kernels have nearly two megabytes of zero padding at the start
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-amd64-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 25 00:05:00 +0000 2024
>Originator:     Taylor R Campbell
>Release:        current, 10, 9, ...
>Organization:
Zzzzzzzzzzzzzzzze NetBSD Foundation
>Environment:
>Description:
$ hexdump -C < netbsd | head -15
00000000  7f 45 4c 46 02 01 01 00  00 00 00 00 00 00 00 00  |.ELF............|
00000010  02 00 3e 00 01 00 00 00  00 e0 20 80 ff ff ff ff  |..>....... .....|
00000020  40 00 00 00 00 00 00 00  e0 27 c3 01 00 00 00 00  |@........'......|
00000030  00 00 00 00 40 00 38 00  02 00 40 00 22 00 21 00  |....@.8...@.".!.|
00000040  01 00 00 00 05 00 00 00  00 00 20 00 00 00 00 00  |.......... .....|
00000050  00 00 20 80 ff ff ff ff  00 00 20 00 00 00 00 00  |.. ....... .....|
00000060  08 f4 4a 01 00 00 00 00  08 f4 4a 01 00 00 00 00  |..J.......J.....|
00000070  00 00 20 00 00 00 00 00  01 00 00 00 06 00 00 00  |.. .............|
00000080  00 00 80 01 00 00 00 00  00 00 80 81 ff ff ff ff  |................|
00000090  00 00 80 01 00 00 00 00  80 21 0c 00 00 00 00 00  |.........!......|
000000a0  00 00 20 00 00 00 00 00  00 00 20 00 00 00 00 00  |.. ....... .....|
000000b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00200000  0f 01 f8 48 a3 08 00 00  00 00 ff ff ff 48 a1 10  |...H.........H..|
00200010  00 00 00 00 ff ff ff 48  c7 40 f8 3f 00 00 00 48  |.......H.@.?...H|

Note the * padding between 0xb0 and 0x200000, presumably some misguided unintentional alignment.

Not really a problem if you always store compressed kernels, but it's rather silly to store this uncompressed.
>How-To-Repeat:
build amd64 or i386 kernels
>Fix:
Yes, please!

Home	PR Database Search