WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: initrd change breaks binary compatibility

To: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: initrd change breaks binary compatibility
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Tue, 10 Oct 2006 15:31:59 -0500
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 10 Oct 2006 13:32:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061010192848.GA795@xxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20061010192848.GA795@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.7 (X11/20060918)
John Levon wrote:
This change in 3.0.3-testing-rc3:

changeset:   11728:30f13007be3f
user:        kfraser@xxxxxxxxxxxxxxxxxxxxx
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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel