All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: phasta@kernel.org
Cc: Ard Biesheuvel <ardb+git@google.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] x86/boot: Work around broken busybox truncate tool
Date: Thu, 24 Apr 2025 18:25:18 +0200	[thread overview]
Message-ID: <aApl7iqRl--uZFZE@gmail.com> (raw)
In-Reply-To: <cc549efcd078fdefafc12442b08ae7ceaa197eb9.camel@mailbox.org>


* Philipp Stanner <phasta@mailbox.org> wrote:

> 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.

Fixed, thx.

> 
> > 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.

So I've added a Fixes tag, because it's informative, but 9c54baab4401 
is new in v6.15-rc1 so there's no backporting need.

> > 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>

Thanks!

	Ingo

  reply	other threads:[~2025-04-24 16:25 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
2025-04-24 16:25   ` Ingo Molnar [this message]
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=aApl7iqRl--uZFZE@gmail.com \
    --to=mingo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.