From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by kanga.kvack.org (Postfix) with ESMTP id 57FD86B0038 for ; Thu, 10 Sep 2015 04:36:09 -0400 (EDT) Received: by wiclk2 with SMTP id lk2so18902195wic.0 for ; Thu, 10 Sep 2015 01:36:08 -0700 (PDT) Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com. [209.85.212.169]) by mx.google.com with ESMTPS id wl9si18144673wjb.188.2015.09.10.01.36.07 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Sep 2015 01:36:08 -0700 (PDT) Received: by wicfx3 with SMTP id fx3so18764687wic.1 for ; Thu, 10 Sep 2015 01:36:07 -0700 (PDT) Date: Thu, 10 Sep 2015 11:36:05 +0300 From: "Kirill A. Shutemov" Subject: Re: Multiple potential races on vma->vm_flags Message-ID: <20150910083605.GB9526@node.dhcp.inet.fi> References: <55EC9221.4040603@oracle.com> <20150907114048.GA5016@node.dhcp.inet.fi> <55F0D5B2.2090205@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55F0D5B2.2090205@oracle.com> Sender: owner-linux-mm@kvack.org List-ID: To: Sasha Levin Cc: Rik van Riel , Andrew Morton , Andrey Konovalov , Dmitry Vyukov , linux-mm@kvack.org, linux-kernel@vger.kernel.org On Wed, Sep 09, 2015 at 08:58:26PM -0400, Sasha Levin wrote: > On 09/07/2015 07:40 AM, Kirill A. Shutemov wrote: > > On Sun, Sep 06, 2015 at 03:21:05PM -0400, Sasha Levin wrote: > >> > ================================================================== > >> > ThreadSanitizer: data-race in munlock_vma_pages_range > >> > > >> > Write of size 8 by thread T378 (K2633, CPU3): > >> > [] munlock_vma_pages_range+0x59/0x3e0 mm/mlock.c:425 > >> > [] mlock_fixup+0x1c9/0x280 mm/mlock.c:549 > >> > [] do_mlock+0x14c/0x180 mm/mlock.c:589 > >> > [< inlined >] SyS_munlock+0x74/0xb0 SYSC_munlock mm/mlock.c:651 > >> > [] SyS_munlock+0x74/0xb0 mm/mlock.c:643 > >> > [] entry_SYSCALL_64_fastpath+0x12/0x71 > >> > arch/x86/entry/entry_64.S:186 > > ... > > > >> > Previous read of size 8 by thread T398 (K2623, CPU2): > >> > [] try_to_unmap_one+0x78/0x4f0 mm/rmap.c:1208 > >> > [< inlined >] rmap_walk+0x147/0x450 rmap_walk_file mm/rmap.c:1540 > >> > [] rmap_walk+0x147/0x450 mm/rmap.c:1559 > >> > [] try_to_munlock+0xa2/0xc0 mm/rmap.c:1423 > >> > [] __munlock_isolated_page+0x30/0x60 mm/mlock.c:129 > >> > [] __munlock_pagevec+0x236/0x3f0 mm/mlock.c:331 > >> > [] munlock_vma_pages_range+0x380/0x3e0 mm/mlock.c:476 > >> > [] mlock_fixup+0x1c9/0x280 mm/mlock.c:549 > >> > [] do_mlock+0x14c/0x180 mm/mlock.c:589 > >> > [< inlined >] SyS_munlock+0x74/0xb0 SYSC_munlock mm/mlock.c:651 > >> > [] SyS_munlock+0x74/0xb0 mm/mlock.c:643 > >> > [] entry_SYSCALL_64_fastpath+0x12/0x71 > >> > arch/x86/entry/entry_64.S:186 > > Okay, the detected race is mlock/munlock vs. rmap. > > > > On rmap side we check vma->vm_flags in few places without taking > > vma->vm_mm->mmap_sem. The vma cannot be freed since we hold i_mmap_rwsem > > or anon_vma_lock, but nothing prevent vma->vm_flags from changing under > > us. > > > > In this particular case, speculative check in beginning of > > try_to_unmap_one() is fine, since we re-check it under mmap_sem later in > > the function. > > So you're suggesting that this isn't the cause of the bad page flags > error observed by Andrey and myself? I don't see it, but who knows. -- Kirill A. Shutemov -- 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