From: Miaohe Lin <linmiaohe@huawei.com>
To: <akpm@linux-foundation.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<linmiaohe@huawei.com>
Subject: [PATCH] mm/mmu_notifiers: use helper function mmu_notifier_synchronize()
Date: Thu, 17 Feb 2022 19:09:48 +0800 [thread overview]
Message-ID: <20220217110948.35477-1-linmiaohe@huawei.com> (raw)
Use helper function mmu_notifier_synchronize() to ensure all mmu_notifiers
are freed. Minor readability improvement.
Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
---
mm/mmu_notifier.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/mm/mmu_notifier.c b/mm/mmu_notifier.c
index 459d195d2ff6..159f70c20236 100644
--- a/mm/mmu_notifier.c
+++ b/mm/mmu_notifier.c
@@ -334,15 +334,15 @@ static void mn_hlist_release(struct mmu_notifier_subscriptions *subscriptions,
srcu_read_unlock(&srcu, id);
/*
- * synchronize_srcu here prevents mmu_notifier_release from returning to
- * exit_mmap (which would proceed with freeing all pages in the mm)
- * until the ->release method returns, if it was invoked by
- * mmu_notifier_unregister.
+ * mmu_notifier_synchronize here prevents mmu_notifier_release from
+ * returning to exit_mmap (which would proceed with freeing all pages
+ * in the mm) until the ->release method returns, if it was invoked
+ * by mmu_notifier_unregister.
*
* The notifier_subscriptions can't go away from under us because
* one mm_count is held by exit_mmap.
*/
- synchronize_srcu(&srcu);
+ mmu_notifier_synchronize();
}
void __mmu_notifier_release(struct mm_struct *mm)
@@ -851,7 +851,7 @@ void mmu_notifier_unregister(struct mmu_notifier *subscription,
* Wait for any running method to finish, of course including
* ->release if it was run by mmu_notifier_release instead of us.
*/
- synchronize_srcu(&srcu);
+ mmu_notifier_synchronize();
BUG_ON(atomic_read(&mm->mm_count) <= 0);
--
2.23.0
next reply other threads:[~2022-02-17 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 11:09 Miaohe Lin [this message]
2022-02-17 13:32 ` Matthew Wilcox
2022-02-17 13:44 ` Miaohe Lin
2022-02-17 15:50 ` Jason Gunthorpe
2022-02-18 1:49 ` Miaohe Lin
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=20220217110948.35477-1-linmiaohe@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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
all inboxes | Powered by JetHome®