From: Dave Hansen <dave.hansen@intel.com>
To: Xiao Guangrong <guangrong.xiao@linux.intel.com>,
pbonzini@redhat.com, akpm@linux-foundation.org, mhocko@suse.com,
dan.j.williams@intel.com
Cc: gleb@kernel.org, mtosatti@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, stefanha@redhat.com,
yuhuang@redhat.com, linux-mm@kvack.org,
ross.zwisler@linux.intel.com
Subject: Re: [PATCH] Fix region lost in /proc/self/smaps
Date: Fri, 9 Sep 2016 09:47:45 -0700 [thread overview]
Message-ID: <57D2E7B1.40201@intel.com> (raw)
In-Reply-To: <01bcbbe2-5560-ea42-4d75-6ab50c3060d4@linux.intel.com>
On 09/09/2016 01:19 AM, Xiao Guangrong wrote:
>
> Yes. I was talking the case as follows:
> 1: read() #1: prints vma-A(0x1000 -> 0x2000)
> 2: unmap vma-A(0x1000 -> 0x2000)
> 3: create vma-B(0x80 -> 0x3000) on other file with different permission
> (w, r, x)
> 4: read #2: prints vma-B(0x2000 -> 0x3000)
>
> Then userspace will get just a portion of vma-B. well, maybe it is not
> too bad. :)
Yeah, I think this is the way to go. Feel free to add my ack.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave.hansen@intel.com>
To: Xiao Guangrong <guangrong.xiao@linux.intel.com>,
pbonzini@redhat.com, akpm@linux-foundation.org, mhocko@suse.com,
dan.j.williams@intel.com
Cc: gleb@kernel.org, mtosatti@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, stefanha@redhat.com,
yuhuang@redhat.com, linux-mm@kvack.org,
ross.zwisler@linux.intel.com
Subject: Re: [PATCH] Fix region lost in /proc/self/smaps
Date: Fri, 9 Sep 2016 09:47:45 -0700 [thread overview]
Message-ID: <57D2E7B1.40201@intel.com> (raw)
In-Reply-To: <01bcbbe2-5560-ea42-4d75-6ab50c3060d4@linux.intel.com>
On 09/09/2016 01:19 AM, Xiao Guangrong wrote:
>
> Yes. I was talking the case as follows:
> 1: read() #1: prints vma-A(0x1000 -> 0x2000)
> 2: unmap vma-A(0x1000 -> 0x2000)
> 3: create vma-B(0x80 -> 0x3000) on other file with different permission
> (w, r, x)
> 4: read #2: prints vma-B(0x2000 -> 0x3000)
>
> Then userspace will get just a portion of vma-B. well, maybe it is not
> too bad. :)
Yeah, I think this is the way to go. Feel free to add my ack.
next prev parent reply other threads:[~2016-09-09 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 6:51 [PATCH] Fix region lost in /proc/self/smaps Xiao Guangrong
2016-09-07 6:51 ` Xiao Guangrong
2016-09-07 7:05 ` Xiao Guangrong
2016-09-07 7:05 ` Xiao Guangrong
2016-09-07 16:34 ` Dave Hansen
2016-09-07 16:34 ` Dave Hansen
2016-09-08 3:36 ` Xiao Guangrong
2016-09-08 3:36 ` Xiao Guangrong
2016-09-08 14:05 ` Dave Hansen
2016-09-08 14:05 ` Dave Hansen
2016-09-09 8:19 ` Xiao Guangrong
2016-09-09 8:19 ` Xiao Guangrong
2016-09-09 16:47 ` Dave Hansen [this message]
2016-09-09 16:47 ` Dave Hansen
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=57D2E7B1.40201@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=gleb@kernel.org \
--cc=guangrong.xiao@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=ross.zwisler@linux.intel.com \
--cc=stefanha@redhat.com \
--cc=yuhuang@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.