[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] libxc: Question on kernel image unzipping



On 09/07/2009 13:34, "Andreas Sommer" <AndiDog@xxxxxx> wrote:

> libxc contains the following function which is used when uncompressing zipped
> kernel images:
> size_t xc_dom_check_gzip(void *blob, size_t ziplen)
> {
>     ...
>     return unziplen + 16;
> }
> The returned unziplen+16 is used for the size of the destination buffer given
> to inflate. But it is then also written to the kernel_size attribute of the
> xc_dom_image struct. Hence kernel_size does not contain the uncompressed
> kernel size but that plus 16.
> So why do you always add 16 bytes to the real uncompressed kernel size?? That
> doesn't make much sense to me but I need to know it because it is related to
> my current work.

Gerd Hoffman would be the person to ask. The +16 doesn't appear to me to
have any purpose.

 -- Keir



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.