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 12:52:45 +0000 [thread overview]
Message-ID: <5106749D.6080005@citrix.com> (raw)
In-Reply-To: <1359374741.6559.70.camel@zakaz.uk.xensource.com>
On 28/01/13 12:05, Ian Campbell wrote:
> On Mon, 2013-01-28 at 11:57 +0000, Andrew Cooper wrote:
>
>> The immediate preceeding function, xc_dom_linux_build returns a struct
>> xc_dom_image * as its second parameter,
> Does it?
>
> Looking at the only caller (the python bindings) I can see that the dom
> paramter is an input parameter to that function and was previously
> allocated via xc_dom_allocate. Looking at the implementation of
> xc_domain_linux_build confirms this.
>
> Ian.
>
Ok - this is turning into far more of a rats nest than I originally thought.
Please ignore the patch while I apply some sanity to our code.
~Andrew
prev parent reply other threads:[~2013-01-28 12:52 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
2013-01-28 12:05 ` Ian Campbell
2013-01-28 12:52 ` Andrew Cooper [this message]
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=5106749D.6080005@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).