From: Davidlohr Bueso <dave@stgolabs.net>
To: Michel Lespinasse <walken@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Laurent Dufour <ldufour@linux.ibm.com>,
Vlastimil Babka <vbabka@suse.cz>,
Matthew Wilcox <willy@infradead.org>,
Liam Howlett <Liam.Howlett@oracle.com>,
Jerome Glisse <jglisse@redhat.com>,
David Rientjes <rientjes@google.com>,
Hugh Dickins <hughd@google.com>, Ying Han <yinghan@google.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Daniel Jordan <daniel.m.jordan@oracle.com>
Subject: Re: [PATCH v4 02/10] MMU notifier: use the new mmap locking API
Date: Mon, 20 Apr 2020 12:51:12 -0700 [thread overview]
Message-ID: <20200420195112.uy7xb4d4kltp6cnz@linux-p48b> (raw)
In-Reply-To: <20200415004353.130248-3-walken@google.com>
On Tue, 14 Apr 2020, Michel Lespinasse wrote:
>This use is converted manually ahead of the next patch in the series,
>as it requires including a new header which the automated conversion
>would miss.
>
>Signed-off-by: Michel Lespinasse <walken@google.com>
>Reviewed-by: Daniel Jordan <daniel.m.jordan@oracle.com>
Reviewed-by: Davidlohr Bueso <dbueso@suse.de>
>---
> include/linux/mmu_notifier.h | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
>diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h
>index 736f6918335e..2f462710a1a4 100644
>--- a/include/linux/mmu_notifier.h
>+++ b/include/linux/mmu_notifier.h
>@@ -5,6 +5,7 @@
> #include <linux/list.h>
> #include <linux/spinlock.h>
> #include <linux/mm_types.h>
>+#include <linux/mmap_lock.h>
> #include <linux/srcu.h>
> #include <linux/interval_tree.h>
>
>@@ -277,9 +278,9 @@ mmu_notifier_get(const struct mmu_notifier_ops *ops, struct mm_struct *mm)
> {
> struct mmu_notifier *ret;
>
>- down_write(&mm->mmap_sem);
>+ mmap_write_lock(mm);
> ret = mmu_notifier_get_locked(ops, mm);
>- up_write(&mm->mmap_sem);
>+ mmap_write_unlock(mm);
> return ret;
> }
> void mmu_notifier_put(struct mmu_notifier *subscription);
>--
>2.26.0.110.g2183baf09c-goog
>
next prev parent reply other threads:[~2020-04-20 19:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 0:43 [PATCH v4 00/10] Add a new mmap locking API wrapping mmap_sem calls Michel Lespinasse
2020-04-15 0:43 ` [PATCH v4 01/10] mmap locking API: initial implementation as rwsem wrappers Michel Lespinasse
2020-04-20 19:48 ` Davidlohr Bueso
2020-04-21 0:48 ` Michel Lespinasse
2020-04-15 0:43 ` [PATCH v4 02/10] MMU notifier: use the new mmap locking API Michel Lespinasse
2020-04-20 19:51 ` Davidlohr Bueso [this message]
2020-04-15 0:43 ` [PATCH v4 03/10] DMA reservations: " Michel Lespinasse
2020-04-15 0:43 ` [PATCH v4 04/10] mmap locking API: use coccinelle to convert mmap_sem rwsem call sites Michel Lespinasse
2020-04-15 0:43 ` [PATCH v4 05/10] mmap locking API: convert mmap_sem call sites missed by coccinelle Michel Lespinasse
2020-04-15 0:43 ` [PATCH v4 06/10] mmap locking API: convert nested write lock sites Michel Lespinasse
2020-04-20 18:19 ` Daniel Jordan
2020-04-20 19:33 ` Matthew Wilcox
2020-04-21 0:51 ` Michel Lespinasse
2020-04-15 0:43 ` [PATCH v4 07/10] mmap locking API: add mmap_read_trylock_non_owner() Michel Lespinasse
2020-04-20 18:22 ` Daniel Jordan
2020-04-20 19:23 ` Matthew Wilcox
2020-04-21 0:55 ` Michel Lespinasse
2020-04-15 0:43 ` [PATCH v4 08/10] mmap locking API: add MMAP_LOCK_INITIALIZER Michel Lespinasse
2020-04-20 18:23 ` Daniel Jordan
2020-04-20 19:28 ` Matthew Wilcox
2020-04-21 0:57 ` Michel Lespinasse
2020-04-15 0:43 ` [PATCH v4 09/10] mmap locking API: use lockdep_assert_held Michel Lespinasse
2020-04-21 2:35 ` Matthew Wilcox
2020-04-15 0:43 ` [PATCH v4 10/10] mmap locking API: rename mmap_sem to mmap_lock Michel Lespinasse
2020-04-20 18:28 ` Daniel Jordan
2020-04-21 5:33 ` kbuild test robot
2020-04-21 22:19 ` Michel Lespinasse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200420195112.uy7xb4d4kltp6cnz@linux-p48b \
--to=dave@stgolabs.net \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.m.jordan@oracle.com \
--cc=hughd@google.com \
--cc=jgg@ziepe.ca \
--cc=jglisse@redhat.com \
--cc=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=walken@google.com \
--cc=willy@infradead.org \
--cc=yinghan@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).