From: Kyungsik Lee <kyungsik.lee@lge.com>
To: Andrew Morton <akpm@linux-foundation.org>,
"Daniel M. Weeks" <dan@danweeks.net>
Cc: "Daniel M. Weeks" <dan@danweeks.net>,
Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
hyojun.im@lge.com, chan.jeong@lge.com
Subject: Re: [PATCH] Fix flags for initramfs LZ4 compression
Date: Wed, 19 Feb 2014 16:51:35 +0900 [thread overview]
Message-ID: <20140219075135.GA5352@hulk> (raw)
In-Reply-To: <20140218160856.235f259bc5865e05e8f24a36@linux-foundation.org>
Hello,
On Tue, Feb 18, 2014 at 04:08:56PM -0800, Andrew Morton wrote:
> On Sat, 15 Feb 2014 18:14:57 -0500 "Daniel M. Weeks" <dan@danweeks.net> wrote:
>
> > LZ4 as implemented in the kernel differs from the default method now
> > used by the reference implementation of LZ4. Until the in-kernel method
> > is updated to support the new default, passing the legacy flag (-l) to
> > the compressor is necessary. Without this flag the kernel-generated,
> > LZ4-compressed initramfs is junk.
> >
> > ...
> >
> > --- a/scripts/gen_initramfs_list.sh
> > +++ b/scripts/gen_initramfs_list.sh
> > @@ -257,7 +257,7 @@ case "$arg" in
> > && compr="lzop -9 -f"
> > echo "$output_file" | grep -q "\.lz4$" \
> > && [ -x "`which lz4 2> /dev/null`" ] \
> > - && compr="lz4 -9 -f"
> > + && compr="lz4 -l -9 -f"
> > echo "$output_file" | grep -q "\.cpio$" && compr="cat"
> > shift
> > ;;
>
> What happens is the user is running an old version of /bin/lz4? A
> version which predates this switch to a new format? Do those earlier
> versions accept -l, even though they don't need it? Or will the kernel
> build fail?
It seems that lz4 supports legacy format with the same option as lz4c
does. Just looking at the first few bytes of lz4 compressed image, we
can see whether it is new format or not.
It shows new format magic number without this patch. New format magic
number is 0x184d2204.
$ hexdump -C ./initramfs_data.cpio.lz4 |more
00000000 04 22 4d 18 64 70 b9 69 (Little Endian)
...
Currently Kernel supports legacy format only.
Acked-by: Kyungsik Lee <kyungsik.lee@lge.com>
Thanks,
Kyungsik
prev parent reply other threads:[~2014-02-19 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 23:14 [PATCH] Fix flags for initramfs LZ4 compression Daniel M. Weeks
2014-02-19 0:06 ` Andrew Morton
2014-02-19 0:08 ` Andrew Morton
2014-02-19 7:51 ` Kyungsik Lee [this message]
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=20140219075135.GA5352@hulk \
--to=kyungsik.lee@lge.com \
--cc=akpm@linux-foundation.org \
--cc=chan.jeong@lge.com \
--cc=dan@danweeks.net \
--cc=hyojun.im@lge.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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