Re: [Xen-devel] Balloon driver bug in increase_reservation

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Mon, 2013-09-02 at 16:04 +0100, Wei Liu wrote:
> On Mon, Sep 02, 2013 at 03:48:43PM +0100, Ian Campbell wrote:
> > On Mon, 2013-09-02 at 15:43 +0100, Wei Liu wrote:
> > > Hi, Stefano
> > > 
> > > I found another bug in the balloon scratch page code. As I didn't follow
> > > the discussion on scratch page so I cannot propose a proper fix at the
> > > moment.
> > > 
> > > The problem is that in balloon.c:increase_reservation, when a ballooned
> > > page is resued, it can have a valid P2M entry pointing to the scratch,
> > > hitting the BUG_ON
> > > 
> > >    BUG_ON(!xen_feature(XENFEAT_auto_translated_physmap) &&
> > >           phys_to_machine_mapping_valid(pfn));
> > > 
> > > As balloon worker might run by a CPU other then the one that returns the
> > > page, checking pfn_to_mfn(pfn) == local_cpu_scratch_page_mfn wouldn't
> > > work.  Checking pfn_to_mfn(pfn) belongs to the set of all scratch page
> > > mfns is not desirable.
> > 
> > This makes me think that whoever suggested that pfn_to_mfn for a
> > ballooned page out to return INVALID_MFN was right.
> > 
> 
> If there are many balloon pages the check can be expensive.

IIRC the suggestion was that the p2m for a ballooned out page would
contain INVALID_MFN, so the expense is just the lookup you would be
doing anyway.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel