From: Juergen Gross <jgross@suse.com>
To: Ian Campbell <ian.campbell@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Wei Liu <wei.liu2@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] tools/libxc: Initialise parameters in map_p2m_list() for error paths
Date: Thu, 7 Jan 2016 16:19:28 +0100 [thread overview]
Message-ID: <568E8200.2000801@suse.com> (raw)
In-Reply-To: <1452179172.21055.232.camel@citrix.com>
On 07/01/16 16:06, Ian Campbell wrote:
> On Thu, 2016-01-07 at 14:55 +0000, Andrew Cooper wrote:
>> c/s 7bf7458 "libxc: support of linear p2m list for migration of
>> pv-domains" breaks compilation on CentOS 7 because of 'ptes' being
>> possibly uninitialised after the 'err:' label.
>>
>> The migration will fail early for conditions which would cause the for()
>> loop not to run, but the compiler doesn't know this.
>
> Isn't the issue the malloc goto err path before the loop? Looks like that
> should have the error behaviour from the earlier half of the function
> rather than the latter.
Yes to both. OTOH with Andrew's patch the code behaves correctly.
> There might also be a path if ctx->x86_pv.levels == 0, in which case the
> loop will never run, that's the sort of thing which could be checked (or
> even perhaps asserted) on entry to the function.
As there is no function vector involved between setting levels and
consuming it I doubt this makes really sense.
Juergen
next prev parent reply other threads:[~2016-01-07 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 14:55 [PATCH] tools/libxc: Initialise parameters in map_p2m_list() for error paths Andrew Cooper
2016-01-07 15:04 ` Wei Liu
2016-01-07 15:06 ` Ian Campbell
2016-01-07 15:19 ` Juergen Gross [this message]
2016-01-07 15:24 ` Andrew Cooper
2016-01-07 15:35 ` Ian Campbell
2016-01-07 15:06 ` Juergen Gross
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=568E8200.2000801@suse.com \
--to=jgross@suse.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=wei.liu2@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).