From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kirill A. Shutemov" Subject: Re: [PATCH v2 5/7] fs/proc/task_mmu.c: simplify the vma_stop() logic Date: Wed, 6 Aug 2014 13:12:45 +0300 Message-ID: <20140806101245.GA30703@node.dhcp.inet.fi> References: <20140805194627.GA30693@redhat.com> <20140805194659.GA30736@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Morton , Alexander Viro , Cyrill Gorcunov , David Howells , "David S. Miller" , "Eric W. Biederman" , "Kirill A. Shutemov" , Peter Zijlstra , Sasha Levin , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Oleg Nesterov Return-path: Content-Disposition: inline In-Reply-To: <20140805194659.GA30736@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, Aug 05, 2014 at 09:46:59PM +0200, Oleg Nesterov wrote: > m_start() drops ->mmap_sem and does mmput() if it retuns vsyscall > vma. This is because in this case m_stop()->vma_stop() obviously > can't use gate_vma->vm_mm. > > Now that we have proc_maps_private->mm we can simplify this logic: > > - Change m_start() to return with ->mmap_sem held unless it returns > IS_ERR_OR_NULL(). > > - Change vma_stop() to use priv->mm and avoid the ugly vma checks, > this makes "vm_area_struct *vma" unnecessary. > > - This also allows m_start() to use vm_stop(). > > - Cleanup m_next() to follow the new locking rule. > > Note: m_stop() looks very ugly, and this temporary uglifies it > even more. Fixed by the next change. > > Signed-off-by: Oleg Nesterov Acked-by: Kirill A. Shutemov -- Kirill A. Shutemov