From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Kravetz Subject: Re: [PATCH v2] mm/mremap: Fail map duplication attempts for private mappings Date: Fri, 21 Jul 2017 14:18:31 -0700 Message-ID: References: <20170720082058.GF9058@dhcp22.suse.cz> <1500583079-26504-1-git-send-email-mike.kravetz@oracle.com> <20170721143644.GC5944@dhcp22.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170721143644.GC5944@dhcp22.suse.cz> Sender: owner-linux-mm@kvack.org To: Michal Hocko Cc: linux-mm@kvack.org, Linux API , linux-kernel@vger.kernel.org, Andrew Morton , Andrea Arcangeli , Aaron Lu , "Kirill A . Shutemov" , Vlastimil Babka , Anshuman Khandual List-Id: linux-api@vger.kernel.org On 07/21/2017 07:36 AM, Michal Hocko wrote: > On Thu 20-07-17 13:37:59, Mike Kravetz wrote: >> mremap will create a 'duplicate' mapping if old_size == 0 is >> specified. Such duplicate mappings make no sense for private >> mappings. > > sorry for the nit picking but this is not true strictly speaking. > It makes some sense, arguably (e.g. take an atomic snapshot of the > mapping). It doesn't make any sense with the _current_ implementation. > >> If duplication is attempted for a private mapping, >> mremap creates a separate private mapping unrelated to the >> original mapping and makes no modifications to the original. >> This is contrary to the purpose of mremap which should return >> a mapping which is in some way related to the original. >> >> Therefore, return EINVAL in the case where if an attempt is >> made to duplicate a private mapping. Also, print a warning >> message (once) if such an attempt is made. >> >> Signed-off-by: Mike Kravetz > > I do not insist on the comment update suggested > http://lkml.kernel.org/r/20170720082058.GF9058@dhcp22.suse.cz > but I would appreciate it... > > Other than that looks reasonably to me > > Acked-by: Michal Hocko My apologies. I overlooked your comment about the comment when creating the patch. Below is the patch with commit message and comment updated. >>From 5c4a1602bd6a942544ed011dc0a72fd258e874b2 Mon Sep 17 00:00:00 2001 From: Mike Kravetz Date: Wed, 12 Jul 2017 13:52:47 -0700 Subject: [PATCH] mm/mremap: Fail map duplication attempts for private mappings mremap will attempt to create a 'duplicate' mapping if old_size == 0 is specified. In the case of private mappings, mremap will actually create a fresh separate private mapping unrelated to the original. This does not fit with the design semantics of mremap as the intention is to create a new mapping based on the original. Therefore, return EINVAL in the case where an attempt is made to duplicate a private mapping. Also, print a warning message (once) if such an attempt is made. Signed-off-by: Mike Kravetz --- mm/mremap.c | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/mm/mremap.c b/mm/mremap.c index cd8a1b1..75b167d 100644 --- a/mm/mremap.c +++ b/mm/mremap.c @@ -383,6 +383,19 @@ static struct vm_area_struct *vma_to_resize(unsigned long addr, if (!vma || vma->vm_start > addr) return ERR_PTR(-EFAULT); + /* + * !old_len is a special case where an attempt is made to 'duplicate' + * a mapping. This makes no sense for private mappings as it will + * instead create a fresh/new mapping unrelated to the original. This + * is contrary to the basic idea of mremap which creates new mappings + * based on the original. There are no known use cases for this + * behavior. As a result, fail such attempts. + */ + if (!old_len && !(vma->vm_flags & (VM_SHARED | VM_MAYSHARE))) { + pr_warn_once("%s (%d): attempted to duplicate a private mapping with mremap. This is not supported.\n", current->comm, current->pid); + return ERR_PTR(-EINVAL); + } + if (is_vm_hugetlb_page(vma)) return ERR_PTR(-EINVAL); -- 2.7.5 -- 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