linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wang YanQing <udknight@gmail.com>
To: Konstantin Khlebnikov <koct9i@gmail.com>
Cc: Mel Gorman <mgorman@suse.de>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	yinghai@kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC] Strange do_munmap in mmap_region
Date: Fri, 20 Mar 2015 23:41:25 +0800	[thread overview]
Message-ID: <20150320154125.GA3168@udknight> (raw)
In-Reply-To: <CALYGNiPjEFLC2uiTGZMqP4TwDBit6+3VaiEpvGELYg8jDsVXBw@mail.gmail.com>

On Thu, Mar 19, 2015 at 06:36:54PM +0300, Konstantin Khlebnikov wrote:
> > Assme process has vma in region 4096-8192, one page size, mapped to
> > a file's first 4096 bytes, then a new map want to create vma in range
> > 0-8192 to map 4096-1288 in file, please tell me what's your meaning:
> > "so everything what was here before is unmapped in process"?
> >
> > Why we can just delete old vma for first 4096 size in file which reside
> > in range 4096-8192 without notify user process? And create the new vma
> > to occupy range 0-8192, do you think "everything" is really the same?
> 
> Old and new vmas are intersects? Then that means userpace asked to
> create new mapping at fixed address, so it tells kernel to unmap
> everything in that range. Without MAP_FIXED kernel always choose free area.
> 

Thanks, Konstantin Khlebnikov, you cure my headache :)

I haven't notice MAP_FIXED.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2015-03-21  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28  6:46 [RFC] Strange do_munmap in mmap_region Wang YanQing
2015-03-19  8:33 ` Konstantin Khlebnikov
2015-03-19 15:12   ` Wang YanQing
2015-03-19 15:36     ` Konstantin Khlebnikov
2015-03-20 15:41       ` Wang YanQing [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=20150320154125.GA3168@udknight \
    --to=udknight@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=koct9i@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).