xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2] xenguest: Alter xsa-25 decompression limit prototypes
Date: Mon, 28 Jan 2013 11:57:09 +0000	[thread overview]
Message-ID: <51066795.5020306@citrix.com> (raw)
In-Reply-To: <1359373846.6559.67.camel@zakaz.uk.xensource.com>

On 28/01/13 11:50, Ian Campbell wrote:
> On Mon, 2013-01-28 at 11:44 +0000, Andrew Cooper wrote:
>> To allow xenguest consumers to make use of the extra protection added as a
>> result of xsa-25.
>>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>>
>> ---
>> Changes since v1:
>>  * Remove prototypes from xc_dom.h to remove duplication
>>
>> diff -r 5af4f2ab06f3 -r 75aafcd809a7 tools/libxc/xc_dom.h
>> --- a/tools/libxc/xc_dom.h
>> +++ b/tools/libxc/xc_dom.h
>> @@ -209,10 +209,7 @@ int xc_dom_mem_init(struct xc_dom_image 
>>  #endif
>>  
>>  int xc_dom_kernel_check_size(struct xc_dom_image *dom, size_t sz);
>> -int xc_dom_kernel_max_size(struct xc_dom_image *dom, size_t sz);
>> -
>>  int xc_dom_ramdisk_check_size(struct xc_dom_image *dom, size_t sz);
>> -int xc_dom_ramdisk_max_size(struct xc_dom_image *dom, size_t sz);
>>  
>>  size_t xc_dom_check_gzip(xc_interface *xch,
>>                       void *blob, size_t ziplen);
>> diff -r 5af4f2ab06f3 -r 75aafcd809a7 tools/libxc/xenguest.h
>> --- a/tools/libxc/xenguest.h
>> +++ b/tools/libxc/xenguest.h
>> @@ -177,6 +177,10 @@ int xc_dom_linux_build(xc_interface *xch
>>  		       unsigned int console_evtchn,
>>  		       unsigned long *console_mfn);
>>  
>> +#define XENCTRL_HAS_DECOMPRESS_LIMITS
>> +int xc_dom_kernel_max_size(struct xc_dom_image *dom, size_t sz);
>> +int xc_dom_ramdisk_max_size(struct xc_dom_image *dom, size_t sz);
> Looking at this a bit closer, do you know where a utility which only
> includes xenguest.h is getting the necessary struct xc_dom_image *
> handle from? None of the functions in xenguest.h seem to return it and
> the only functions I can find which do are in xc_dom.h...
>
> This seems to be true for the two existing functions in xenguest.h which
> take such a handle as well.
>
> The only in tree caller seems to be the Python bindings, and they just
> include xc_dom.h. Is there some reason why the ocaml tools can't just do
> this?
>
> Ian.
>

The immediate preceeding function, xc_dom_linux_build returns a struct
xc_dom_image * as its second parameter, to allow the user of xenguest to
manage the structure (in so far as it can be managed without the full
declaration).

~Andrew

  reply	other threads:[~2013-01-28 11:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 11:44 [PATCH v2] xenguest: Alter xsa-25 decompression limit prototypes Andrew Cooper
2013-01-28 11:50 ` Ian Campbell
2013-01-28 11:57   ` Andrew Cooper [this message]
2013-01-28 12:05     ` Ian Campbell
2013-01-28 12:52       ` Andrew Cooper

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=51066795.5020306@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).