xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Olaf Hering <olaf@aepfle.de>,
	Andres Lagar-Cavilla <andres@lagarcavilla.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [xen-unstable bisection] complete build-amd64
Date: Thu, 26 Jan 2012 17:38:43 +0000	[thread overview]
Message-ID: <CB474023.29C50%keir.xen@gmail.com> (raw)
In-Reply-To: <20257.36117.343474.863135@mariner.uk.xensource.com>

On 26/01/2012 17:27, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:

> xen.org writes ("[xen-unstable bisection] complete build-amd64"):
>> branch xen-unstable
>> xen branch xen-unstable
>> job build-amd64
>> test xen-build
>> 
>> Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git
>> Tree: xen http://xenbits.xen.org/staging/xen-unstable.hg
>> 
>> *** Found and reproduced problem changeset ***
>> 
>>   Bug is in tree:  xen http://xenbits.xen.org/staging/xen-unstable.hg
>>   Bug introduced:  d5b706214616
>>   Bug not present: 1e27e827e6a8
>> 
>> 
>>   changeset:   24566:d5b706214616
>>   user:        Olaf Hering <olaf@aepfle.de>
>>   date:        Thu Jan 26 11:04:59 2012 +0000
>>       
>>       tools/libxc: fix error handling in xc_mem_paging_load
>>       
>>       xc_mem_paging_load() does not pass errors in errno and the actual
>>       errno from xc_mem_event_control() is overwritten by munlock().
>>       xenpaging_populate_page() needs to check errno, but with the switch to
>>       xc_mem_paging_load() it could not receive ENOMEM anymore.
>>       
>>       Update xc_mem_paging_load() to return -1 and preserve errno during
>>       munlock().
>>       
>>       Signed-off-by: Olaf Hering <olaf@aepfle.de>
>>       Acked-by: Andres Lagar-Cavilla <andres@lagarcavilla.org>
>>       Committed-by: Keir Fraser <keir@xen.org>
> 
> cc1: warnings being treated as errors
> xc_mem_paging.c: In function 'xc_mem_paging_load':
> xc_mem_paging.c:90: error: statement with no effect
> make[3]: *** [xc_mem_paging.o] Error 1
> make[3]: Leaving directory
> `/home/osstest/build.11617.build-amd64/xen-unstable/stubdom/libxc-x86_64'
> make[2]: *** [build] Error 2
> make[2]: Leaving directory
> `/home/osstest/build.11617.build-amd64/xen-unstable/stubdom/libxc-x86_64'
> make[1]: *** [libxc-x86_64/libxenctrl.a] Error 2
> make[1]: *** Waiting for unfinished jobs....

Tim already fixed it.

 -- Keir

  reply	other threads:[~2012-01-26 17:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 17:23 [xen-unstable bisection] complete build-amd64 xen.org
2012-01-26 17:27 ` Ian Jackson
2012-01-26 17:38   ` Keir Fraser [this message]
2012-01-26 17:39     ` Ian Jackson
2012-01-27  9:51   ` Olaf Hering
  -- strict thread matches above, loose matches on Subject: below --
2013-01-11 16:46 xen.org
2012-11-30 22:01 xen.org
2012-01-14  0:43 xen.org
2011-12-02 20:35 xen.org
2011-11-23  0:24 xen.org
2011-09-13 15:27 xen.org
2010-12-03 17:29 xen.org
2010-12-03 17:40 ` Ian Jackson
2010-12-02  5:41 xen.org

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=CB474023.29C50%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=andres@lagarcavilla.org \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xensource.com \
    /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).