From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Weimer Subject: Re: [patch] mremap.2: Add description of old_size == 0 functionality Date: Mon, 25 Sep 2017 16:54:39 +0200 Message-ID: References: <20170915213745.6821-1-mike.kravetz@oracle.com> <20170925123508.pzjbe7wgwagnr5li@dhcp22.suse.cz> <20170925125207.4tu24sbpnihljknu@dhcp22.suse.cz> <765cd0cb-aa35-187c-456d-05d8752caa04@redhat.com> <20170925145238.gic2n37ffc6ytyvx@dhcp22.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170925145238.gic2n37ffc6ytyvx@dhcp22.suse.cz> Content-Language: en-US Sender: owner-linux-mm@kvack.org To: Michal Hocko Cc: Mike Kravetz , mtk.manpages@gmail.com, linux-man@vger.kernel.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, Andrea Arcangeli , "Kirill A . Shutemov" , Vlastimil Babka , Anshuman Khandual , linux-mm@kvack.org List-Id: linux-api@vger.kernel.org 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: email@kvack.org