From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9B537C433DF for ; Mon, 18 May 2020 11:01:37 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 6796C207F5 for ; Mon, 18 May 2020 11:01:37 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6796C207F5 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id A3CEE900003; Mon, 18 May 2020 07:01:36 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 9A013900002; Mon, 18 May 2020 07:01:36 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 88F2D900003; Mon, 18 May 2020 07:01:36 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0195.hostedemail.com [216.40.44.195]) by kanga.kvack.org (Postfix) with ESMTP id 6E560900002 for ; Mon, 18 May 2020 07:01:36 -0400 (EDT) Received: from smtpin18.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 28F2C181AEF10 for ; Mon, 18 May 2020 11:01:36 +0000 (UTC) X-FDA: 76829548992.18.eyes67_6541cb391e51d X-HE-Tag: eyes67_6541cb391e51d X-Filterd-Recvd-Size: 3643 Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf18.hostedemail.com (Postfix) with ESMTP for ; Mon, 18 May 2020 11:01:35 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id B9328ABBD; Mon, 18 May 2020 11:01:36 +0000 (UTC) Subject: Re: [PATCH v5.5 09/10] mmap locking API: add mmap_assert_locked() and mmap_assert_write_locked() To: Michel Lespinasse , Matthew Wilcox Cc: Andrew Morton , linux-mm , LKML , Peter Zijlstra , Laurent Dufour , Liam Howlett , Jerome Glisse , Davidlohr Bueso , David Rientjes , Hugh Dickins , Ying Han , Jason Gunthorpe , Daniel Jordan References: <20200422001422.232330-1-walken@google.com> <20200422001422.232330-11-walken@google.com> <20200422015829.GR5820@bombadil.infradead.org> <20200423015917.GA13910@bombadil.infradead.org> <20200424012612.GA158937@google.com> <20200424013858.GB158937@google.com> From: Vlastimil Babka Message-ID: Date: Mon, 18 May 2020 13:01:33 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200424013858.GB158937@google.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 4/24/20 3:38 AM, Michel Lespinasse wrote: > Add new APIs to assert that mmap_sem is held. > > Using this instead of rwsem_is_locked and lockdep_assert_held[_write] > makes the assertions more tolerant of future changes to the lock type. > > Signed-off-by: Michel Lespinasse > --- > arch/x86/events/core.c | 2 +- > fs/userfaultfd.c | 6 +++--- > include/linux/mmap_lock.h | 14 ++++++++++++++ > mm/gup.c | 2 +- > mm/hmm.c | 2 +- > mm/memory.c | 2 +- > mm/mmu_notifier.c | 6 +++--- > mm/pagewalk.c | 6 +++--- > mm/util.c | 2 +- > 9 files changed, 28 insertions(+), 14 deletions(-) > ... > @@ -73,4 +75,16 @@ static inline void mmap_read_unlock_non_owner(struct mm_struct *mm) > up_read_non_owner(&mm->mmap_sem); > } > > +static inline void mmap_assert_locked(struct mm_struct *mm) > +{ > + VM_BUG_ON_MM(!lockdep_is_held_type(&mm->mmap_sem, -1), mm); > + VM_BUG_ON_MM(!rwsem_is_locked(&mm->mmap_sem), mm); > +} > + > +static inline void mmap_assert_write_locked(struct mm_struct *mm) > +{ > + VM_BUG_ON_MM(!lockdep_is_held_type(&mm->mmap_sem, 0), mm); > + VM_BUG_ON_MM(!rwsem_is_locked(&mm->mmap_sem), mm); > +} I would remove VM_BUG_ON_MM() from the lockdep part. If kernel has lockdep enabled, it's already in heavy debugging mode enough so let's just use it and not depend on DEBUG_VM. Many sites you convert don't require DEBUG_VM for the lockdep checks. With that you can also use the standard lockdep_assert_held() and lockdep_assert_held_write() wrappers. If user has both lockdep and DEBUG_VM enabled, should we run both variants? Perhaps lockdep is enough as it's more comprehensive? Your initial v5 version was doing that.