All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, willy@infradead.org,
	peterx@redhat.com, akpm@linux-foundation.org,
	aarcange@redhat.com, ira.weiny@intel.com,
	akpm@linux-foundation.org
Subject: + mm-userfaultfd-replace-kmap-kmap_atomic-with-kmap_local_page-v2.patch added to mm-hotfixes-unstable branch
Date: Tue, 25 Oct 2022 19:03:40 -0700	[thread overview]
Message-ID: <20221026020342.18FF2C433D6@smtp.kernel.org> (raw)


The patch titled
     Subject: mm-userfaultfd-replace-kmap-kmap_atomic-with-kmap_local_page-v2
has been added to the -mm mm-hotfixes-unstable branch.  Its filename is
     mm-userfaultfd-replace-kmap-kmap_atomic-with-kmap_local_page-v2.patch

This patch will shortly appear at
     https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-userfaultfd-replace-kmap-kmap_atomic-with-kmap_local_page-v2.patch

This patch will later appear in the mm-hotfixes-unstable branch at
    git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***

The -mm tree is included into linux-next via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days

------------------------------------------------------
From: Ira Weiny <ira.weiny@intel.com>
Subject: mm-userfaultfd-replace-kmap-kmap_atomic-with-kmap_local_page-v2
Date: Tue, 25 Oct 2022 15:01:36 -0700

Update the commit message and comment based on additional discussion

Thanks to Matt for pointing out the deadlock potential despite recursive
reads.  

Link: https://lkml.kernel.org/r/20221025220136.2366143-1-ira.weiny@intel.com
Signed-off-by: Ira Weiny <ira.weiny@intel.com>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: Peter Xu <peterx@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---


--- a/mm/userfaultfd.c~mm-userfaultfd-replace-kmap-kmap_atomic-with-kmap_local_page-v2
+++ a/mm/userfaultfd.c
@@ -159,9 +159,19 @@ static int mcopy_atomic_pte(struct mm_st
 
 		page_kaddr = kmap_local_page(page);
 		/*
-		 * The mmap_lock is held here.  Disable page faults to
-		 * prevent deadlock should copy_from_user() fault.  The
-		 * copy will be retried outside the mmap_lock.
+		 * The read mmap_lock is held here.  Despite the
+		 * mmap_lock being read recursive a deadlock is still
+		 * possible if a writer has taken a lock.  For example:
+		 *
+		 * process A thread 1 takes read lock on own mmap_lock
+		 * process A thread 2 calls mmap, blocks taking write lock
+		 * process B thread 1 takes page fault, read lock on own mmap lock
+		 * process B thread 2 calls mmap, blocks taking write lock
+		 * process A thread 1 blocks taking read lock on process B
+		 * process B thread 1 blocks taking read lock on process A
+		 *
+		 * Disable page faults to prevent potential deadlock
+		 * and retry the copy outside the mmap_lock.
 		 */
 		pagefault_disable();
 		ret = copy_from_user(page_kaddr,
_

Patches currently in -mm which might be from ira.weiny@intel.com are

mm-userfaultfd-replace-kmap-kmap_atomic-with-kmap_local_page.patch
mm-userfaultfd-replace-kmap-kmap_atomic-with-kmap_local_page-v2.patch


                 reply	other threads:[~2022-10-26  2:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221026020342.18FF2C433D6@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=aarcange@redhat.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=peterx@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.