lkml.org 
[lkml]   [2006]   [Nov]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Re : vm: weird behaviour when munmapping
From
Date
On Fri, 2006-11-17 at 12:50 +0000, moreau francis wrote:
> Peter Zijlstra wrote:
> >
> > http://lwn.net/Kernel/LDD3/
> >
> > Chapter 15. Section 'Virtual Memory Areas'.
> >
> > Basically; vm_ops->open() is not called on the first vma. With this
> > munmap() you split the area in two, and it so happens the new vma is the
> > lower one.
> >
>
> since I did "munmap(0x2aaae000, 1024)" I would say that the the new vma
> is the _upper_ one.
>
> lower vma: 0x2aaae000 -> 0x2aaaf000
> upper vma: 0x2aaaf000 -> 0x2aab2000

that is the remaining VMA, not the new one; we trigger this code:

/* Does it split the last one? */
last = find_vma(mm, end);
if (last && end > last->vm_start) {
int error = split_vma(mm, last, end, 1);
if (error)
return error;
}

So, since its the last VMA that needs to be split (there is only one),
the new VMA is constructed before the old one. Like so:

AAAAAAAAAAAAAAAAAAAAA
BBBBAAAAAAAAAAAAAAAAA

Then you proceed closing, in this case the new one: B.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-11-17 14:11    [W:0.051 / U:0.880 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site