From: Florian Weimer <fweimer@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Mike Kravetz <mike.kravetz@oracle.com>,
mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
Andrea Arcangeli <aarcange@redhat.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Vlastimil Babka <vbabka@suse.cz>,
Anshuman Khandual <khandual@linux.vnet.ibm.com>,
linux-mm@kvack.org
Subject: Re: [patch] mremap.2: Add description of old_size == 0 functionality
Date: Mon, 25 Sep 2017 16:54:39 +0200 [thread overview]
Message-ID: <d06a26f1-5509-bd85-74bc-b08c3db0cb0d@redhat.com> (raw)
In-Reply-To: <20170925145238.gic2n37ffc6ytyvx@dhcp22.suse.cz>
On 09/25/2017 04:52 PM, Michal Hocko wrote:
> On Mon 25-09-17 15:16:09, Florian Weimer wrote:
>> On 09/25/2017 02:52 PM, Michal Hocko wrote:
>>> So, how are you going to deal with the CoW and the implementation which
>>> basically means that the newm mmap content is not the same as the
>>> original one?
>>
>> I don't understand why CoW would kick in.
>
> So you can guarantee nobody is going to write to that memory?
It's mapped readable and executable, but not writable. So the only
thing that could interfere would be a debugger.
Thanks,
Florian
--
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>
next prev parent reply other threads:[~2017-09-25 14:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170915213745.6821-1-mike.kravetz@oracle.com>
2017-09-15 21:53 ` Mike Kravetz
2017-09-18 13:45 ` Florian Weimer
2017-09-18 17:11 ` Mike Kravetz
2017-09-19 12:11 ` Florian Weimer
2017-09-19 21:42 ` [patch v2] " Mike Kravetz
2017-09-20 7:25 ` Michael Kerrisk (man-pages)
2017-09-25 12:36 ` Michal Hocko
2017-09-25 12:40 ` Michael Kerrisk (man-pages)
2017-09-25 16:33 ` Mike Kravetz
2017-09-25 19:26 ` Michael Kerrisk (man-pages)
2017-09-25 12:35 ` [patch] " Michal Hocko
2017-09-25 12:40 ` Florian Weimer
2017-09-25 12:52 ` Michal Hocko
2017-09-25 13:16 ` Florian Weimer
2017-09-25 14:52 ` Michal Hocko
2017-09-25 14:54 ` Florian Weimer [this message]
2017-09-18 1:52 ` Jann Horn
2017-09-18 17:19 ` Mike Kravetz
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=d06a26f1-5509-bd85-74bc-b08c3db0cb0d@redhat.com \
--to=fweimer@redhat.com \
--cc=aarcange@redhat.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=mtk.manpages@gmail.com \
--cc=vbabka@suse.cz \
/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