From: Anthony Liguori <aliguori@us.ibm.com>
To: John Levon <levon@movementarian.org>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: initrd change breaks binary compatibility
Date: Tue, 10 Oct 2006 15:31:59 -0500 [thread overview]
Message-ID: <452C033F.6010005@us.ibm.com> (raw)
In-Reply-To: <20061010192848.GA795@totally.trollied.org>
John Levon wrote:
> This change in 3.0.3-testing-rc3:
>
> changeset: 11728:30f13007be3f
> user: kfraser@localhost.localdomain
> date: Mon Oct 09 13:50:00 2006 +0100
> files: tools/libxc/xc_linux_build.c
> description:
> [XEND] No need to decompress the initrd when building a domain.
>
> breaks binary compatibility. In particular, it breaks Solaris, which
> expects both grub and xen to uncompress the initrd for us. And it does
> seem odd to differ from grub's behaviour needlessly.
>
> I don't know what causes the broken Linux initrd's that the commit
> message refers to, but it seems they need to be fixed another way.
I suspect that we're actually broken here. I think the way we determine
the uncompressed size (by reading the last couple bytes) is not
something that can, in generally, be safely relied upon.
We could work around this by decompressing the initrd and dynamically
expanding the buffer we're decompressing to as needed.
Regards,
Anthony Liguori
> regards,
> john
next prev parent reply other threads:[~2006-10-10 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 19:28 initrd change breaks binary compatibility John Levon
2006-10-10 20:31 ` Anthony Liguori [this message]
2006-10-10 20:42 ` Keir Fraser
2006-10-10 21:34 ` John Levon
2006-10-10 21:26 ` Keir Fraser
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=452C033F.6010005@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=levon@movementarian.org \
--cc=xen-devel@lists.xensource.com \
/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.