Received: by 10.192.165.148 with SMTP id m20csp3087653imm; Sun, 22 Apr 2018 23:45:09 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+KRIY9Dwk4b+K2CUabroV6aRbPjtev3ZY5aVrTGzuw5iH6/HBQAqs/5cxuTv2RQ161XFZ/ X-Received: by 10.167.128.194 with SMTP id a2mr18881060pfn.130.1524465909738; Sun, 22 Apr 2018 23:45:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524465909; cv=none; d=google.com; s=arc-20160816; b=hY298Qx5qE5n9YLvEwApn2cgshjdKlkxmyTrtS5g+NSKT4Oe2lmh/VzD5XlVbbdFxq /ogUS+xyxgOpX7xJM/gq218HsKEQDfI0TmQjm8YmKrXCCt3E+AIfOWPUdmvHz4KxZ4h0 q6W85M0yxL82/wiSpivTaIYrPRCY5IsCqrC5qz/v6vmlhrcyHUYFYGzi5jxZWsErwzRZ s5NY09f08dQDjHefucPe0uiKrc5+5c/LKXT/kzH4WQLzNoOj2P61FlVbt5MmKM8kKVnN /h9R6K3PfN1tklPysVgdSWEM/13Tiiltcer/1gnqUFb5grlNpRuPqS81lXpqn7XVKiwj Gdiw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=H+7WyCLWtu13+K+c02E2Y2DmHEw/3VnkApnaMEZ2NII=; b=w0DzHrEsT8No8NFQeKbwsKKjLZqsx89JSykM3xp4flBuI7QWOfXT1dqL7/ih9Jy+63 Ra1nh8nn7GSb6Dxc1qTMbvEhKoKunKlIQbyj6HlvaIXg8IwdSrK63IooiIke/S3VT2T0 svwmf/MEHz2x6rRUr4/GwltQFDzXWqXR9qSEVdjBL2o2aK01uJkx8/9gM9GrptE8ljq/ 1wia+PclCjAJYhFAFChz9d4iDrYt2SKk0fd82daaFSe3iboZlP5KzKf8fjmp86JRijJH gSq3I65USnovo5gv0BX7wb2XeWpO+JFJvmYVhDZ56Cro/esnEMq3R3TihhanGm10p8Nt HdHA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=jcokk51y; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 9-v6si11312774plb.415.2018.04.22.23.44.55; Sun, 22 Apr 2018 23:45:09 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=jcokk51y; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754094AbeDWGnN (ORCPT + 99 others); Mon, 23 Apr 2018 02:43:13 -0400 Received: from mail-pf0-f193.google.com ([209.85.192.193]:42882 "EHLO mail-pf0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751268AbeDWGnK (ORCPT ); Mon, 23 Apr 2018 02:43:10 -0400 Received: by mail-pf0-f193.google.com with SMTP id o16so8426051pfk.9 for ; Sun, 22 Apr 2018 23:43:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=H+7WyCLWtu13+K+c02E2Y2DmHEw/3VnkApnaMEZ2NII=; b=jcokk51ySH4oWK4PGP5AeRX7JTf12ABx2FtS4lyDERYNrdgRCOvk0NlIftz7ZbwkMS HMeWNNEM+xY8pOyi4uLHxBxQ5XHPYk++8YjS+aFHaNP6Xbbdf+1KZPad/5LL6svVpvvz GC92VxpcCT5pL6FbBYXA2QCQzM9kyCsJqpcWbuR4NM84xI/sAHCsfxM/XmTn+/Zx6Uf/ OtR2KK9Qmg133HYV7WZ8orpT7nCOT4mLIbYBVHGc8Onzs+7G4XVG8q3mGNz+kBGGkGwU tQ0T/jW1SwGb9ZPZlWzWoHvZlLnZWZk3E+sNCqhEbSAfOJUpir1v3IRy9Zp3D3MSdTxz EQrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=H+7WyCLWtu13+K+c02E2Y2DmHEw/3VnkApnaMEZ2NII=; b=cg8rl5ziFdCBhvuVWFc9iOaKlWcm/L3J6h/jVfw2JEZYGxnuFqYh+F3Ga8qyaJArhH xGYcnZA8kix2mRqCPOF2DA/Qlg/pIBN/RGNJ66Sfrls+Er7CE3mSuI/W/jeCL/jmFDM1 mJTffgat/XbGNZ4Y3L7+hk90wlk1vbi17ZkfAua9JJ6k02r/onZeb0EJSt4ge0pH17WQ n6y638eoxi0Ce7oAKTr8JYyyW/P1ZUP5NKARmAQVg7e9D0Aun5KQSTTgsc0i3iRV03wJ ztU1qV3R9nBjvwLiwrAQCSFnaLMx95wRHntN2BvO1rQ5Eyo1FdjRCTz7pJolN/ulb6Su NL+g== X-Gm-Message-State: ALQs6tDW8zrGWTeNUH4poBh5NGnm3a3rVz1k638cYyx79WgDq6FvQm4K ecmyxsxE1iQZ1GwvDMYz01U= X-Received: by 2002:a17:902:9686:: with SMTP id n6-v6mr19247369plp.136.1524465790151; Sun, 22 Apr 2018 23:43:10 -0700 (PDT) Received: from rodete-desktop-imager.corp.google.com ([2401:fa00:d:10:affa:813f:5380:6613]) by smtp.gmail.com with ESMTPSA id c201sm21076952pfb.30.2018.04.22.23.43.01 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 22 Apr 2018 23:43:08 -0700 (PDT) Date: Mon, 23 Apr 2018 15:42:59 +0900 From: Minchan Kim To: Laurent Dufour Cc: akpm@linux-foundation.org, mhocko@kernel.org, peterz@infradead.org, kirill@shutemov.name, ak@linux.intel.com, dave@stgolabs.net, jack@suse.cz, Matthew Wilcox , benh@kernel.crashing.org, mpe@ellerman.id.au, paulus@samba.org, Thomas Gleixner , Ingo Molnar , hpa@zytor.com, Will Deacon , Sergey Senozhatsky , Andrea Arcangeli , Alexei Starovoitov , kemi.wang@intel.com, sergey.senozhatsky.work@gmail.com, Daniel Jordan , David Rientjes , Jerome Glisse , Ganesh Mahendran , linux-kernel@vger.kernel.org, linux-mm@kvack.org, haren@linux.vnet.ibm.com, khandual@linux.vnet.ibm.com, npiggin@gmail.com, bsingharora@gmail.com, paulmck@linux.vnet.ibm.com, Tim Chen , linuxppc-dev@lists.ozlabs.org, x86@kernel.org Subject: Re: [PATCH v10 08/25] mm: VMA sequence count Message-ID: <20180423064259.GC114098@rodete-desktop-imager.corp.google.com> References: <1523975611-15978-1-git-send-email-ldufour@linux.vnet.ibm.com> <1523975611-15978-9-git-send-email-ldufour@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1523975611-15978-9-git-send-email-ldufour@linux.vnet.ibm.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 17, 2018 at 04:33:14PM +0200, Laurent Dufour wrote: > From: Peter Zijlstra > > Wrap the VMA modifications (vma_adjust/unmap_page_range) with sequence > counts such that we can easily test if a VMA is changed. So, seqcount is to protect modifying all attributes of vma? > > The unmap_page_range() one allows us to make assumptions about > page-tables; when we find the seqcount hasn't changed we can assume > page-tables are still valid. Hmm, seqcount covers page-table, too. Please describe what the seqcount want to protect. > > The flip side is that we cannot distinguish between a vma_adjust() and > the unmap_page_range() -- where with the former we could have > re-checked the vma bounds against the address. > > Signed-off-by: Peter Zijlstra (Intel) > > [Port to 4.12 kernel] > [Build depends on CONFIG_SPECULATIVE_PAGE_FAULT] > [Introduce vm_write_* inline function depending on > CONFIG_SPECULATIVE_PAGE_FAULT] > [Fix lock dependency between mapping->i_mmap_rwsem and vma->vm_sequence by > using vm_raw_write* functions] > [Fix a lock dependency warning in mmap_region() when entering the error > path] > [move sequence initialisation INIT_VMA()] > Signed-off-by: Laurent Dufour > --- > include/linux/mm.h | 44 ++++++++++++++++++++++++++++++++++++++++++++ > include/linux/mm_types.h | 3 +++ > mm/memory.c | 2 ++ > mm/mmap.c | 31 +++++++++++++++++++++++++++++++ > 4 files changed, 80 insertions(+) > > diff --git a/include/linux/mm.h b/include/linux/mm.h > index efc1248b82bd..988daf7030c9 100644 > --- a/include/linux/mm.h > +++ b/include/linux/mm.h > @@ -1264,6 +1264,9 @@ struct zap_details { > static inline void INIT_VMA(struct vm_area_struct *vma) > { > INIT_LIST_HEAD(&vma->anon_vma_chain); > +#ifdef CONFIG_SPECULATIVE_PAGE_FAULT > + seqcount_init(&vma->vm_sequence); > +#endif > } > > struct page *_vm_normal_page(struct vm_area_struct *vma, unsigned long addr, > @@ -1386,6 +1389,47 @@ static inline void unmap_shared_mapping_range(struct address_space *mapping, > unmap_mapping_range(mapping, holebegin, holelen, 0); > } > > +#ifdef CONFIG_SPECULATIVE_PAGE_FAULT > +static inline void vm_write_begin(struct vm_area_struct *vma) > +{ > + write_seqcount_begin(&vma->vm_sequence); > +} > +static inline void vm_write_begin_nested(struct vm_area_struct *vma, > + int subclass) > +{ > + write_seqcount_begin_nested(&vma->vm_sequence, subclass); > +} > +static inline void vm_write_end(struct vm_area_struct *vma) > +{ > + write_seqcount_end(&vma->vm_sequence); > +} > +static inline void vm_raw_write_begin(struct vm_area_struct *vma) > +{ > + raw_write_seqcount_begin(&vma->vm_sequence); > +} > +static inline void vm_raw_write_end(struct vm_area_struct *vma) > +{ > + raw_write_seqcount_end(&vma->vm_sequence); > +} > +#else > +static inline void vm_write_begin(struct vm_area_struct *vma) > +{ > +} > +static inline void vm_write_begin_nested(struct vm_area_struct *vma, > + int subclass) > +{ > +} > +static inline void vm_write_end(struct vm_area_struct *vma) > +{ > +} > +static inline void vm_raw_write_begin(struct vm_area_struct *vma) > +{ > +} > +static inline void vm_raw_write_end(struct vm_area_struct *vma) > +{ > +} > +#endif /* CONFIG_SPECULATIVE_PAGE_FAULT */ > + > extern int access_process_vm(struct task_struct *tsk, unsigned long addr, > void *buf, int len, unsigned int gup_flags); > extern int access_remote_vm(struct mm_struct *mm, unsigned long addr, > diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h > index 21612347d311..db5e9d630e7a 100644 > --- a/include/linux/mm_types.h > +++ b/include/linux/mm_types.h > @@ -335,6 +335,9 @@ struct vm_area_struct { > struct mempolicy *vm_policy; /* NUMA policy for the VMA */ > #endif > struct vm_userfaultfd_ctx vm_userfaultfd_ctx; > +#ifdef CONFIG_SPECULATIVE_PAGE_FAULT > + seqcount_t vm_sequence; > +#endif > } __randomize_layout; > > struct core_thread { > diff --git a/mm/memory.c b/mm/memory.c > index f86efcb8e268..f7fed053df80 100644 > --- a/mm/memory.c > +++ b/mm/memory.c > @@ -1503,6 +1503,7 @@ void unmap_page_range(struct mmu_gather *tlb, > unsigned long next; > > BUG_ON(addr >= end); The comment about saying it aims for page-table stability will help. > + vm_write_begin(vma); > tlb_start_vma(tlb, vma); > pgd = pgd_offset(vma->vm_mm, addr); > do { > @@ -1512,6 +1513,7 @@ void unmap_page_range(struct mmu_gather *tlb, > next = zap_p4d_range(tlb, vma, pgd, addr, next, details); > } while (pgd++, addr = next, addr != end); > tlb_end_vma(tlb, vma); > + vm_write_end(vma); > } > > > diff --git a/mm/mmap.c b/mm/mmap.c > index 8bd9ae1dfacc..813e49589ea1 100644 > --- a/mm/mmap.c > +++ b/mm/mmap.c > @@ -692,6 +692,30 @@ int __vma_adjust(struct vm_area_struct *vma, unsigned long start, > long adjust_next = 0; > int remove_next = 0; > > + /* > + * Why using vm_raw_write*() functions here to avoid lockdep's warning ? > + * > + * Locked is complaining about a theoretical lock dependency, involving > + * 3 locks: > + * mapping->i_mmap_rwsem --> vma->vm_sequence --> fs_reclaim > + * > + * Here are the major path leading to this dependency : > + * 1. __vma_adjust() mmap_sem -> vm_sequence -> i_mmap_rwsem > + * 2. move_vmap() mmap_sem -> vm_sequence -> fs_reclaim > + * 3. __alloc_pages_nodemask() fs_reclaim -> i_mmap_rwsem > + * 4. unmap_mapping_range() i_mmap_rwsem -> vm_sequence > + * > + * So there is no way to solve this easily, especially because in > + * unmap_mapping_range() the i_mmap_rwsem is grab while the impacted > + * VMAs are not yet known. > + * However, the way the vm_seq is used is guarantying that we will > + * never block on it since we just check for its value and never wait > + * for it to move, see vma_has_changed() and handle_speculative_fault(). > + */ > + vm_raw_write_begin(vma); > + if (next) > + vm_raw_write_begin(next); > + > if (next && !insert) { > struct vm_area_struct *exporter = NULL, *importer = NULL; > > @@ -902,6 +926,7 @@ int __vma_adjust(struct vm_area_struct *vma, unsigned long start, > anon_vma_merge(vma, next); > mm->map_count--; > mpol_put(vma_policy(next)); > + vm_raw_write_end(next); > kmem_cache_free(vm_area_cachep, next); > /* > * In mprotect's case 6 (see comments on vma_merge), > @@ -916,6 +941,8 @@ int __vma_adjust(struct vm_area_struct *vma, unsigned long start, > * "vma->vm_next" gap must be updated. > */ > next = vma->vm_next; > + if (next) > + vm_raw_write_begin(next); > } else { > /* > * For the scope of the comment "next" and > @@ -962,6 +989,10 @@ int __vma_adjust(struct vm_area_struct *vma, unsigned long start, > if (insert && file) > uprobe_mmap(insert); > > + if (next && next != vma) > + vm_raw_write_end(next); > + vm_raw_write_end(vma); > + > validate_mm(mm); > > return 0; > -- > 2.7.4 >