From: Greg KH <gregkh@linuxfoundation.org>
To: Parth Pancholi <parth105105@gmail.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
Parth Pancholi <parth.pancholi@toradex.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v2] kbuild: switch from lz4c to lz4 for compression
Date: Thu, 14 Nov 2024 17:02:01 +0100 [thread overview]
Message-ID: <2024111442-yeast-flail-fcea@gregkh> (raw)
In-Reply-To: <20241114145645.563356-1-parth105105@gmail.com>
On Thu, Nov 14, 2024 at 03:56:44PM +0100, Parth Pancholi wrote:
> From: Parth Pancholi <parth.pancholi@toradex.com>
>
> Replace lz4c with lz4 for kernel image compression.
> Although lz4 and lz4c are functionally similar, lz4c has been deprecated
> upstream since 2018. Since as early as Ubuntu 16.04 and Fedora 25, lz4
> and lz4c have been packaged together, making it safe to update the
> requirement from lz4c to lz4.
>
> Consequently, some distributions and build systems, such as OpenEmbedded,
> have fully transitioned to using lz4. OpenEmbedded core adopted this
> change in commit fe167e082cbd ("bitbake.conf: require lz4 instead of
> lz4c"), causing compatibility issues when building the mainline kernel
> in the latest OpenEmbedded environment, as seen in the errors below.
>
> This change also updates the LZ4 compression commands to make it backward
> compatible by replacing stdin and stdout with the '-' option, due to some
> unclear reason, the stdout keyword does not work for lz4 and '-' works for
> both. In addition, this modifies the legacy '-c1' with '-9' which is also
> compatible with both. This fixes the mainline kernel build failures with
> the latest master OpenEmbedded builds associated with the mentioned
> compatibility issues.
>
> LZ4 arch/arm/boot/compressed/piggy_data
> /bin/sh: 1: lz4c: not found
> ...
> ...
> ERROR: oe_runmake failed
>
> Cc: stable@vger.kernel.org
What bug does this resolve that it needs to be backported to stable
kernels?
thanks,
greg k-h
next prev parent reply other threads:[~2024-11-14 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 14:56 [PATCH v2] kbuild: switch from lz4c to lz4 for compression Parth Pancholi
2024-11-14 16:02 ` Greg KH [this message]
2024-11-15 8:39 ` Francesco Dolcini
2024-11-15 9:22 ` Greg KH
2024-11-15 9:45 ` Francesco Dolcini
2024-11-16 7:51 ` Masahiro Yamada
2025-02-02 9:00 ` Salvatore Bonaccorso
2025-02-03 2:44 ` Masahiro Yamada
2025-02-04 13:52 ` Greg KH
2025-02-03 12:37 ` Sasha Levin
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=2024111442-yeast-flail-fcea@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=francesco.dolcini@toradex.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=parth.pancholi@toradex.com \
--cc=parth105105@gmail.com \
--cc=stable@vger.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.