The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Philipp Stanner <phasta@mailbox.org>
To: Ard Biesheuvel <ardb+git@google.com>, linux-kernel@vger.kernel.org
Cc: x86@kernel.org, Ard Biesheuvel <ardb@kernel.org>, phasta@kernel.org
Subject: Re: [PATCH] x86/boot: Work around broken busybox truncate tool
Date: Thu, 24 Apr 2025 12:22:32 +0200	[thread overview]
Message-ID: <cc549efcd078fdefafc12442b08ae7ceaa197eb9.camel@mailbox.org> (raw)
In-Reply-To: <20250424101917.1552527-2-ardb+git@google.com>

Thank you very much for this fix :)

On Thu, 2025-04-24 at 12:19 +0200, Ard Biesheuvel wrote:
> From: Ard Biesheuvel <ardb@kernel.org>
> 
> The GNU coreutils version of truncate, which is the original, accepts
> a
> % prefix for the -s size argument which means the file in question
> should be padded to a multiple of the given size. This is currently
> used
> to pad the setup block of bzImage to a multiple of 4k before
> appending
> the decompressor.
> 
> busybux reimplements truncate but does not support this idiom, and

typo, busybox.

> therefore fails the build since commit
> 
>   9c54baab4401 ("x86/boot: Drop CRC-32 checksum and the build tool
> that generates it")

Should this be marked as an official bug?

If so, I'd put this as a Fixes: tag below.

> 
> Work around this by avoiding truncate altogether, and relying on dd
> to
> perform the padding.
> 
> Reported-by: <phasta@kernel.org>

Tested-by: Philipp Stanner <phasta@kernel.org>


Thx,

P.

> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> ---
> I personally think using a busybox environment for building the
> kernel
> is a terrible idea, and does not satisfy the build tool requirements
> listed in the documentation. But apparently, it used to work and now
> it
> doesn't, and the workaround is rather straight-forward.
> 
> IOW, I don't care whether this gets applied or not, so I will leave
> it
> to others to make the argument.
> 
>  arch/x86/boot/Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/x86/boot/Makefile b/arch/x86/boot/Makefile
> index 81f55da81967..640fcac3af74 100644
> --- a/arch/x86/boot/Makefile
> +++ b/arch/x86/boot/Makefile
> @@ -59,7 +59,7 @@ KBUILD_CFLAGS	+= $(CONFIG_CC_IMPLICIT_FALLTHROUGH)
>  $(obj)/bzImage: asflags-y  := $(SVGA_MODE)
>  
>  quiet_cmd_image = BUILD   $@
> -      cmd_image = cp $< $@; truncate -s %4K $@; cat
> $(obj)/vmlinux.bin >>$@
> +      cmd_image = (dd if=$< bs=4k conv=sync status=none; cat
> $(filter-out $<,$(real-prereqs))) >$@
>  
>  $(obj)/bzImage: $(obj)/setup.bin $(obj)/vmlinux.bin FORCE
>  	$(call if_changed,image)


  reply	other threads:[~2025-04-24 10:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 10:19 [PATCH] x86/boot: Work around broken busybox truncate tool Ard Biesheuvel
2025-04-24 10:22 ` Philipp Stanner [this message]
2025-04-24 16:25   ` Ingo Molnar
2025-04-24 16:29 ` Ingo Molnar
2025-04-24 16:39   ` Ard Biesheuvel
2025-04-30 12:00     ` David Laight
2025-04-24 16:45 ` [tip: x86/urgent] x86/boot: Work around broken busybox 'truncate' tool tip-bot2 for Ard Biesheuvel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cc549efcd078fdefafc12442b08ae7ceaa197eb9.camel@mailbox.org \
    --to=phasta@mailbox.org \
    --cc=ardb+git@google.com \
    --cc=ardb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phasta@kernel.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox