linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lespinasse <walken@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Laurent Dufour <ldufour@linux.ibm.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	 Matthew Wilcox <willy@infradead.org>,
	"Liam R . Howlett" <Liam.Howlett@oracle.com>,
	 Jerome Glisse <jglisse@redhat.com>,
	Davidlohr Bueso <dave@stgolabs.net>,
	 David Rientjes <rientjes@google.com>
Cc: linux-mm <linux-mm@kvack.org>, Michel Lespinasse <walken@google.com>
Subject: [RFC PATCH 05/24] MM locking API: allow for sleeping during unlock
Date: Mon, 24 Feb 2020 12:30:38 -0800	[thread overview]
Message-ID: <20200224203057.162467-6-walken@google.com> (raw)
In-Reply-To: <20200224203057.162467-1-walken@google.com>

Following changes will implement fine-grained range locks for the
MM locking API, using a data structure to represent the existing
locks, and a mutex to protect that data structure.

As a result, we need to prepare for the possibility that unlocking
a memory range may need to sleep when acquiring that mutex.

Signed-off-by: Michel Lespinasse <walken@google.com>
---
 kernel/bpf/stackmap.c      | 6 +++++-
 kernel/exit.c              | 2 +-
 mm/mm_lock_rwsem_checked.c | 3 +++
 3 files changed, 9 insertions(+), 2 deletions(-)

diff --git kernel/bpf/stackmap.c kernel/bpf/stackmap.c
index ba2399ce00e4..0f483abeb94c 100644
--- kernel/bpf/stackmap.c
+++ kernel/bpf/stackmap.c
@@ -308,8 +308,12 @@ static void stack_map_get_build_id_offset(struct bpf_stack_build_id *id_offs,
 	 *
 	 * Same fallback is used for kernel stack (!user) on a stackmap
 	 * with build_id.
+	 *
+	 * FIXME - currently disabling the build_id lookup feature
+	 * as mm_read_range_unlock() may block, which is not always
+	 * possible to do here.
 	 */
-	if (!user || !current || !current->mm || irq_work_busy ||
+	if (true || !user || !current || !current->mm || irq_work_busy ||
 	    !mm_read_range_trylock(current->mm, mm_range_ptr)) {
 		/* cannot access current->mm, fall back to ips */
 		for (i = 0; i < trace_nr; i++) {
diff --git kernel/exit.c kernel/exit.c
index 9a0b72562adb..60ec6efb4e2c 100644
--- kernel/exit.c
+++ kernel/exit.c
@@ -478,9 +478,9 @@ static void exit_mm(void)
 	/* more a memory barrier than a real lock */
 	task_lock(current);
 	current->mm = NULL;
-	mm_read_unlock(mm);
 	enter_lazy_tlb(mm, current);
 	task_unlock(current);
+	mm_read_unlock(mm);
 	mm_update_next_owner(mm);
 	mmput(mm);
 	if (test_thread_flag(TIF_MEMDIE))
diff --git mm/mm_lock_rwsem_checked.c mm/mm_lock_rwsem_checked.c
index 3551deb85e3d..e45d1a598c87 100644
--- mm/mm_lock_rwsem_checked.c
+++ mm/mm_lock_rwsem_checked.c
@@ -61,6 +61,7 @@ EXPORT_SYMBOL(mm_write_range_trylock);
 
 void mm_write_range_unlock(struct mm_struct *mm, struct mm_lock_range *range)
 {
+	might_sleep();
 	if (range->mm != mm)
 		mm_lock_dump("mm_write_range_unlock");
 	range->mm = NULL;
@@ -113,6 +114,7 @@ EXPORT_SYMBOL(mm_read_range_trylock);
 
 void mm_read_range_unlock(struct mm_struct *mm, struct mm_lock_range *range)
 {
+	might_sleep();
 	if (range->mm != mm)
 		mm_lock_dump("mm_read_range_unlock");
 	range->mm = NULL;
@@ -123,6 +125,7 @@ EXPORT_SYMBOL(mm_read_range_unlock);
 void mm_read_range_unlock_non_owner(struct mm_struct *mm,
 				    struct mm_lock_range *range)
 {
+	might_sleep();
 	if (range->mm != mm)
 		mm_lock_dump("mm_read_range_unlock_non_owner");
 	range->mm = NULL;
-- 
2.25.0.341.g760bfbb309-goog



  parent reply	other threads:[~2020-02-24 20:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 20:30 [RFC PATCH 00/24] Fine grained MM locking Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 01/24] MM locking API: initial implementation as rwsem wrappers Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 02/24] MM locking API: use coccinelle to convert mmap_sem rwsem call sites Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 03/24] MM locking API: manual conversion of mmap_sem call sites missed by coccinelle Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 04/24] MM locking API: add range arguments Michel Lespinasse
2020-02-24 20:30 ` Michel Lespinasse [this message]
2020-02-24 20:30 ` [RFC PATCH 06/24] MM locking API: implement fine grained range locks Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 07/24] mm/memory: add range field to struct vm_fault Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 08/24] mm/memory: allow specifying MM lock range to handle_mm_fault() Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 09/24] do_swap_page: use the vmf->range field when dropping mmap_sem Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 10/24] handle_userfault: " Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 11/24] x86 fault handler: merge bad_area() functions Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 12/24] x86 fault handler: use an explicit MM lock range Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 13/24] mm/memory: add prepare_mm_fault() function Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 14/24] mm/swap_state: disable swap vma readahead Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 15/24] x86 fault handler: use a pseudo-vma when operating on anonymous vmas Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 16/24] MM locking API: add vma locking API Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 17/24] x86 fault handler: implement range locking Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 18/24] shared file mappings: use the vmf->range field when dropping mmap_sem Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 19/24] mm: add field to annotate vm_operations that support range locking Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 20/24] x86 fault handler: extend range locking to supported file vmas Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 21/24] do_mmap: add locked argument Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 22/24] do_mmap: implement " Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 23/24] do_mmap: use locked=false in vm_mmap_pgoff() and aio_setup_ring() Michel Lespinasse
2020-02-24 20:30 ` [RFC PATCH 24/24] do_mmap: implement easiest cases of fine grained locking Michel Lespinasse
2022-03-20 22:08 ` [RFC PATCH 00/24] Fine grained MM locking Barry Song
2022-03-20 23:14   ` Matthew Wilcox
2022-03-21  0:20     ` Barry Song

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=20200224203057.162467-6-walken@google.com \
    --to=walken@google.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave@stgolabs.net \
    --cc=jglisse@redhat.com \
    --cc=ldufour@linux.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=peterz@infradead.org \
    --cc=rientjes@google.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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