From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754543AbbGAPtQ (ORCPT ); Wed, 1 Jul 2015 11:49:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50544 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753316AbbGAPtH (ORCPT ); Wed, 1 Jul 2015 11:49:07 -0400 Date: Wed, 1 Jul 2015 17:47:43 +0200 From: Oleg Nesterov To: David Rientjes Cc: Andrew Morton , Al Viro , Benjamin LaHaise , Hugh Dickins , Jeff Moyer , Kirill Shutemov , linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/4] mremap: don't do mm_populate(new_addr) on failure Message-ID: <20150701154743.GB14934@redhat.com> References: <20150619231915.GA25884@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/30, David Rientjes wrote: > > On Sat, 20 Jun 2015, Oleg Nesterov wrote: > > > --- a/mm/mremap.c > > +++ b/mm/mremap.c > > @@ -574,8 +574,10 @@ SYSCALL_DEFINE5(mremap, unsigned long, addr, unsigned long, old_len, > > ret = move_vma(vma, addr, old_len, new_len, new_addr, &locked); > > } > > out: > > - if (ret & ~PAGE_MASK) > > + if (ret & ~PAGE_MASK) { > > vm_unacct_memory(charged); > > + locked = 0; > > + } > > up_write(¤t->mm->mmap_sem); > > if (locked && new_len > old_len) > > mm_populate(new_addr + old_len, new_len - old_len); > > Perhaps I'm looking at the wrong tree (next-20150630), but why does > setting locked to 0 here matter if it's unreferenced? See the "if (locked && ...)" check before mm_populate(). We should not do this if move_vma() fails. Oleg.