From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] grub2 should not unzip Linux initramfs
Date: Tue, 12 Nov 2013 21:03:51 +0100 [thread overview]
Message-ID: <528289A7.2010501@gmail.com> (raw)
In-Reply-To: <52820237.6090205@schwaighofer.name>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
Committed, thanks.
On 12.11.2013 11:25, Lukas Schwaighofer wrote:
> Hi,
>
> the initramfs protocol (see [1]) supports multiple concatenated archives.
>
> Because of grub2's implicit unzipping of gz-compressed multiboot
> modules, a valid initramfs-file (e.g. in my case containing of two
> concatenated gz-files) may be rendered unbootable.
>
> I have attached the trivial patch adding --nounzip to the the
> appropriate module-directive when generating XEN boot entries. As this
> resembles the behavior when booting without XEN (using the grub2
> commands linux and initrd) more closely I don't expect any problems.
>
> I have reported this to the Debian bugtracker before [2] with no
> response, but I suppose this is the correct point to report this issue.
>
> Thank you
> Lukas
>
>
> [1]
> https://www.kernel.org/doc/Documentation/early-userspace/buffer-format.txt
> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700197
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
prev parent reply other threads:[~2013-11-12 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 10:25 [PATCH] grub2 should not unzip Linux initramfs Lukas Schwaighofer
2013-11-12 20:03 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=528289A7.2010501@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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.