From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@citrix.com>, xen-devel@lists.xenproject.org
Cc: Wei.Liu2@citrix.com, stefano.stabellini@citrix.com,
Ian Jackson <ian.jackson@eu.citrix.com>
Subject: Re: [PATCH for-4.6] tools/libxc: arm: Check the index before accessing the bank
Date: Fri, 18 Sep 2015 09:52:44 +0100 [thread overview]
Message-ID: <1442566364.18856.251.camel@citrix.com> (raw)
In-Reply-To: <55FAFB9D.7090107@citrix.com>
On Thu, 2015-09-17 at 18:42 +0100, Julien Grall wrote:
> On 17/09/15 18:36, Julien Grall wrote:
> > When creating a guest with more than 3GB of memory, the 2 banks will be
> > used and the loop with overrunning. The code will fail later on because
> > Xen will deny to populate the region:
> >
> > domainbuilder: detail: xc_dom_devicetree_mem: called
> > domainbuilder: detail: xc_dom_mem_init: mem 3096 MB, pages 0xc1800
> > pages, 4k each
> > domainbuilder: detail: xc_dom_mem_init: 0xc1800 pages
> > domainbuilder: detail: xc_dom_boot_mem_init: called
> > domainbuilder: detail: set_mode: guest xen-3.0-aarch64, address size 64
> > domainbuilder: detail: xc_dom_malloc : 14384 kB
> > domainbuilder: detail: populate_guest_memory: populating RAM
> > @0000000040000000-0000000100000000 (3072MB)
> > domainbuilder: detail: populate_one_size: populated 0x3/0x3 entries
> > with shift 18
> > domainbuilder: detail: populate_guest_memory: populating RAM
> > @0000000200000000-0000000201800000 (24MB)
> > domainbuilder: detail: populate_one_size: populated 0xc/0xc entries
> > with shift 9
> > domainbuilder: detail: populate_guest_memory: populating RAM
> > @0000007fad41c000-0007fb39dd42c000 (2141954816MB)
> > domainbuilder: detail: populate_one_size: populated 0x100/0x1e4 entries
> > with shift 0
> > domainbuilder: detail: populate_guest_memory: Not enough RAM
> >
> > This is because we are currently accessing the bank before checking the
> > validity of the index. AFAICT, on Debian Jessie, the compiler (gcc
> > 4.9.2) is
> > assuming that it's not necessary to verify the index because it's used
> > before. This is a valid assumption because the operand of && are
> > execute from from left to right.
> >
> > Re-order the checks to verify the validity of the index before
> > accessing
> > the bank.
> >
> > The problem has been present since the introduction of the multi-bank
> > feature in commit 45d9867837f099e9eed4189dac5ed39d1fe2ed49 " tools:
> > arm:
> > prepare domain builder for multiple banks of guest RAM".
>
> Hmmmm I forgot my Signed-off-by :(.
>
> Signed-off-by: Julien Grall <julien.grall@citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
This is a no brainer for 4.6 (and further) IMHO and with Wei not being
around I shall plan to apply later today unless there are objections.
Ian.
>
> > ---
> > Cc: Wei Liu <wei.liu2@citrix.com>
> > Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> >
> > This patch is a candidate for Xen 4.6 and backport to Xen 4.5. Without
> > it, it's impossible to boot guest using more than 3GB (limit after
> > which
> > the memory bank is used).
> > ---
> > tools/libxc/xc_dom_arm.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/libxc/xc_dom_arm.c b/tools/libxc/xc_dom_arm.c
> > index b00d667..aeaba54 100644
> > --- a/tools/libxc/xc_dom_arm.c
> > +++ b/tools/libxc/xc_dom_arm.c
> > @@ -460,7 +460,7 @@ int arch_setup_meminit(struct xc_dom_image *dom)
> > dom->p2m_host[pfn] = INVALID_P2M_ENTRY;
> >
> > /* setup initial p2m and allocate guest memory */
> > - for ( i = 0; dom->rambank_size[i] && i < GUEST_RAM_BANKS; i++ )
> > + for ( i = 0; i < GUEST_RAM_BANKS && dom->rambank_size[i]; i++ )
> > {
> > if ((rc = populate_guest_memory(dom,
> > bankbase[i] >> XC_PAGE_SHIFT,
> >
>
>
next prev parent reply other threads:[~2015-09-18 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 17:36 [PATCH for-4.6] tools/libxc: arm: Check the index before accessing the bank Julien Grall
2015-09-17 17:42 ` Julien Grall
2015-09-18 8:52 ` Ian Campbell [this message]
2015-09-18 10:30 ` Wei Liu
2015-09-21 11:54 ` Ian Campbell
2015-09-25 12:26 ` Ian Campbell
2015-09-28 15:41 ` Ian Campbell
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=1442566364.18856.251.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Wei.Liu2@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xenproject.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).