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

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

On 10/10/06 9:31 pm, "Anthony Liguori" <aliguori@xxxxxxxxxx> wrote:

>> 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.

Yes, we'll do this after 3.0.3-0. It's just a little bit too tricky to slip
in for the release. Unfortunately we have seen some (SLES9) initrd images
with this issue. Presumably they get built in a way that ends up padding
them to a multiple of a 'block' or something like that. It can be fixed by
laundering the initrd through gzip, of course.

 -- Keir



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