From: Andrew Morton <akpm@linux-foundation.org>
To: akuster <akuster@mvista.com>
Cc: ioe-lkml@rameria.de, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/1] MM: detach_vmas_to_be_unmapped fix
Date: Tue, 27 Feb 2007 12:27:27 -0800 [thread overview]
Message-ID: <20070227122727.3bc61fbf.akpm@linux-foundation.org> (raw)
In-Reply-To: <45DF15D4.6040403@mvista.com>
> On Fri, 23 Feb 2007 08:27:00 -0800 akuster <akuster@mvista.com> wrote:
> Wolfgang Wander submitted a fix to address a mmap fragmentation issue.
> The git patch ( 1363c3cd8603a913a27e2995dccbd70d5312d8e6 ) is somewhat
> different and yields different results when running Wolfgang's test case
> leakme.c.
>
> IMHO, the vm start and end address are swapped in arch_unmap_area and
> arch_unmap_area_topdown functions.
>
> Prior to this patch arch_unmap_area() used area->vm_start and
> arch_unmap_area_topdown used area->vm_end in the git patch the following
> change showed up.
>
> if (mm->unmap_area == arch_unmap_area)
> addr = prev ? prev->vm_start : mm->mmap_base;
> else
> addr = vma ? vma->vm_end : mm->mmap_base;
>
> Using Wolfgang Wander's leakme.c test, I get the same results seen with
> his original "Avoiding mmap fragmentation" patch as I do after swapping
> the start & end address in the above code segment. The patch I
> submitted addresses this typo issue.
That's still not an adequate or terribly useful changlog, sorry.
Please tell us exactly what this patch does, without referring to some other
patch which I cannot remember nor presently access.
I particular, before-and-after testing results would be useful so we can
see what the effect of this change is.
Also, please send a Signed-of-by: for this work, thanks.
prev parent reply other threads:[~2007-02-27 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 18:06 [patch 1/1] MM: detach_vmas_to_be_unmapped fix akuster
2007-02-21 20:59 ` Ingo Oeser
2007-02-23 16:27 ` akuster
2007-02-27 20:27 ` Andrew Morton [this message]
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=20070227122727.3bc61fbf.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=akuster@mvista.com \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.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