From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, Keir Fraser <keir@xen.org>
Subject: Re: Ping: [PATCH] fix off-by-one mistakes in vm_alloc()
Date: Mon, 5 Aug 2013 15:54:22 +0100 [thread overview]
Message-ID: <51FFBC9E.60008@citrix.com> (raw)
In-Reply-To: <51FFBFE302000078000E94AF@nat28.tlf.novell.com>
On 05/08/13 14:08, Jan Beulich wrote:
> Ping? (This is expected to fix recurring testsuite failures.)
>
>>>> On 18.07.13 at 11:59, "Jan Beulich" <JBeulich@suse.com> wrote:
>> Also add another pair of assertions to catch eventual further cases of
>> incorrect accounting, and remove the temporary debuggin messages again
>> which commit 68caac7f ("x86: don't use destroy_xen_mappings() for
>> vunmap()") added.
>>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
(Tentatively, if I have followed the logic correctly)
Reviewed-by Andrew Cooper <andrew.cooper3@citrix.com>
>>
>> --- a/xen/common/vmap.c
>> +++ b/xen/common/vmap.c
>> @@ -57,8 +57,8 @@ void *vm_alloc(unsigned int nr, unsigned
>> {
>> struct page_info *pg;
>>
>> - ASSERT(!test_bit(vm_low, vm_bitmap));
>> - for ( start = vm_low; ; )
>> + ASSERT(vm_low == vm_top || !test_bit(vm_low, vm_bitmap));
>> + for ( start = vm_low; start < vm_top; )
>> {
>> bit = find_next_bit(vm_bitmap, vm_top, start + 1);
>> if ( bit > vm_top )
>> @@ -68,12 +68,18 @@ void *vm_alloc(unsigned int nr, unsigned
>> * corresponding page a guard one.
>> */
>> start = (start + align) & ~(align - 1);
>> - if ( start + nr <= bit )
>> - break;
>> - start = bit < vm_top ?
>> - find_next_zero_bit(vm_bitmap, vm_top, bit + 1) : bit;
>> - if ( start >= vm_top )
>> - break;
>> + if ( bit < vm_top )
>> + {
>> + if ( start + nr < bit )
>> + break;
>> + start = find_next_zero_bit(vm_bitmap, vm_top, bit + 1);
>> + }
>> + else
>> + {
>> + if ( start + nr <= bit )
>> + break;
>> + start = bit;
>> + }
>> }
>>
>> if ( start < vm_top )
>> @@ -115,6 +121,10 @@ void *vm_alloc(unsigned int nr, unsigned
>>
>> for ( bit = start; bit < start + nr; ++bit )
>> __set_bit(bit, vm_bitmap);
>> + if ( bit < vm_top )
>> + ASSERT(!test_bit(bit, vm_bitmap));
>> + else
>> + ASSERT(bit == vm_top);
>> if ( start <= vm_low + 2 )
>> vm_low = bit;
>> spin_unlock(&vm_lock);
>> @@ -177,7 +187,6 @@ void *__vmap(const unsigned long *mfn, u
>> void *va = vm_alloc(nr * granularity, align);
>> unsigned long cur = (unsigned long)va;
>>
>> -printk("vmap(%p:%#x)\n", va, nr * granularity);//temp
>> for ( ; va && nr--; ++mfn, cur += PAGE_SIZE * granularity )
>> {
>> if ( map_pages_to_xen(cur, *mfn, granularity, flags) )
>> @@ -202,7 +211,6 @@ void vunmap(const void *va)
>>
>> destroy_xen_mappings(addr, addr + PAGE_SIZE * vm_size(va));
>> #else /* Avoid tearing down intermediate page tables. */
>> -printk("vunmap(%p:%#x)\n", va, vm_size(va));//temp
>> map_pages_to_xen((unsigned long)va, 0, vm_size(va), _PAGE_NONE);
>> #endif
>> vm_free(va);
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-08-05 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 9:59 [PATCH] fix off-by-one mistakes in vm_alloc() Jan Beulich
2013-08-05 13:08 ` Ping: " Jan Beulich
2013-08-05 14:54 ` Andrew Cooper [this message]
2013-08-05 16:03 ` Keir Fraser
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=51FFBC9E.60008@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--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).