From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: paulmck@linux.vnet.ibm.com, peterz@infradead.org,
akpm@linux-foundation.org, kirill@shutemov.name,
ak@linux.intel.com, mhocko@kernel.org, dave@stgolabs.net,
jack@suse.cz, Matthew Wilcox <willy@infradead.org>,
benh@kernel.crashing.org, mpe@ellerman.id.au, paulus@samba.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
hpa@zytor.com, Will Deacon <will.deacon@arm.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
kemi.wang@intel.com, sergey.senozhatsky.work@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
haren@linux.vnet.ibm.com, khandual@linux.vnet.ibm.com,
npiggin@gmail.com, bsingharora@gmail.com,
Tim Chen <tim.c.chen@linux.intel.com>,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org
Subject: [PATCH v6 18/24] mm: Try spin lock in speculative path
Date: Fri, 12 Jan 2018 18:26:02 +0100 [thread overview]
Message-ID: <1515777968-867-19-git-send-email-ldufour@linux.vnet.ibm.com> (raw)
In-Reply-To: <1515777968-867-1-git-send-email-ldufour@linux.vnet.ibm.com>
There is a deadlock when a CPU is doing a speculative page fault and
another one is calling do_unmap().
The deadlock occurred because the speculative path try to spinlock the
pte while the interrupt are disabled. When the other CPU in the
unmap's path has locked the pte then is waiting for all the CPU to
invalidate the TLB. As the CPU doing the speculative fault have the
interrupt disable it can't invalidate the TLB, and can't get the lock.
Since we are in a speculative path, we can race with other mm action.
So let assume that the lock may not get acquired and fail the
speculative page fault.
Here are the stacks captured during the deadlock:
CPU 0
native_flush_tlb_others+0x7c/0x260
flush_tlb_mm_range+0x6a/0x220
tlb_flush_mmu_tlbonly+0x63/0xc0
unmap_page_range+0x897/0x9d0
? unmap_single_vma+0x7d/0xe0
? release_pages+0x2b3/0x360
unmap_single_vma+0x7d/0xe0
unmap_vmas+0x51/0xa0
unmap_region+0xbd/0x130
do_munmap+0x279/0x460
SyS_munmap+0x53/0x70
CPU 1
do_raw_spin_lock+0x14e/0x160
_raw_spin_lock+0x5d/0x80
? pte_map_lock+0x169/0x1b0
pte_map_lock+0x169/0x1b0
handle_pte_fault+0xbf2/0xd80
? trace_hardirqs_on+0xd/0x10
handle_speculative_fault+0x272/0x280
handle_speculative_fault+0x5/0x280
__do_page_fault+0x187/0x580
trace_do_page_fault+0x52/0x260
do_async_page_fault+0x19/0x70
async_page_fault+0x28/0x30
Signed-off-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
---
mm/memory.c | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/mm/memory.c b/mm/memory.c
index 96720cc7ca74..83640079d407 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -2472,7 +2472,8 @@ static bool pte_spinlock(struct vm_fault *vmf)
goto out;
vmf->ptl = pte_lockptr(vmf->vma->vm_mm, vmf->pmd);
- spin_lock(vmf->ptl);
+ if (unlikely(!spin_trylock(vmf->ptl)))
+ goto out;
if (vma_has_changed(vmf)) {
spin_unlock(vmf->ptl);
@@ -2526,8 +2527,20 @@ static bool pte_map_lock(struct vm_fault *vmf)
if (!pmd_same(pmdval, vmf->orig_pmd))
goto out;
- pte = pte_offset_map_lock(vmf->vma->vm_mm, vmf->pmd,
- vmf->address, &ptl);
+ /*
+ * Same as pte_offset_map_lock() except that we call
+ * spin_trylock() in place of spin_lock() to avoid race with
+ * unmap path which may have the lock and wait for this CPU
+ * to invalidate TLB but this CPU has irq disabled.
+ * Since we are in a speculative patch, accept it could fail
+ */
+ ptl = pte_lockptr(vmf->vma->vm_mm, vmf->pmd);
+ pte = pte_offset_map(vmf->pmd, vmf->address);
+ if (unlikely(!spin_trylock(ptl))) {
+ pte_unmap(pte);
+ goto out;
+ }
+
if (vma_has_changed(vmf)) {
pte_unmap_unlock(pte, ptl);
goto out;
--
2.7.4
next prev parent reply other threads:[~2018-01-12 17:27 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 17:25 [PATCH v6 00/24] Speculative page faults Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 01/24] x86/mm: Define CONFIG_SPF Laurent Dufour
2018-01-12 18:57 ` Thomas Gleixner
2018-01-15 17:37 ` Laurent Dufour
2018-01-15 17:49 ` Thomas Gleixner
2018-01-15 18:37 ` Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 02/24] powerpc/mm: " Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 03/24] mm: Dont assume page-table invariance during faults Laurent Dufour
2018-01-17 3:04 ` Andi Kleen
2018-01-17 8:57 ` Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 04/24] mm: Prepare for FAULT_FLAG_SPECULATIVE Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 05/24] mm: Introduce pte_spinlock " Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 06/24] mm: VMA sequence count Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 07/24] mm: Protect VMA modifications using " Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 08/24] mm: protect mremap() against SPF hanlder Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 09/24] mm: Protect SPF handler against anon_vma changes Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 10/24] mm: Cache some VMA fields in the vm_fault structure Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 11/24] mm/migrate: Pass vm_fault pointer to migrate_misplaced_page() Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 12/24] mm: Introduce __lru_cache_add_active_or_unevictable Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 13/24] mm: Introduce __maybe_mkwrite() Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 14/24] mm: Introduce __vm_normal_page() Laurent Dufour
2018-01-12 17:25 ` [PATCH v6 15/24] mm: Introduce __page_add_new_anon_rmap() Laurent Dufour
2018-01-12 17:26 ` [PATCH v6 16/24] mm: Protect mm_rb tree with a rwlock Laurent Dufour
2018-01-12 18:48 ` Matthew Wilcox
2018-01-15 17:42 ` Laurent Dufour
2018-01-12 17:26 ` [PATCH v6 17/24] mm: Provide speculative fault infrastructure Laurent Dufour
2018-01-12 17:26 ` Laurent Dufour [this message]
2018-01-12 18:18 ` [PATCH v6 18/24] mm: Try spin lock in speculative path Matthew Wilcox
2018-01-16 13:24 ` Laurent Dufour
2018-01-12 17:26 ` [PATCH v6 19/24] mm: Adding speculative page fault failure trace events Laurent Dufour
2018-01-12 17:26 ` [PATCH v6 20/24] perf: Add a speculative page fault sw event Laurent Dufour
2018-01-12 17:26 ` [PATCH v6 21/24] perf tools: Add support for the SPF perf event Laurent Dufour
2018-01-12 17:26 ` [PATCH v6 22/24] mm: Speculative page fault handler return VMA Laurent Dufour
2018-01-12 19:02 ` Matthew Wilcox
2018-01-13 4:23 ` Matthew Wilcox
2018-01-16 14:47 ` Laurent Dufour
2018-01-16 14:58 ` Matthew Wilcox
2018-01-12 17:26 ` [PATCH v6 23/24] x86/mm: Add speculative pagefault handling Laurent Dufour
2018-01-12 17:26 ` [PATCH v6 24/24] powerpc/mm: Add speculative page fault Laurent Dufour
2018-01-16 15:11 ` [PATCH v6 00/24] Speculative page faults Kirill A. Shutemov
2018-01-17 15:15 ` Laurent Dufour
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=1515777968-867-19-git-send-email-ldufour@linux.vnet.ibm.com \
--to=ldufour@linux.vnet.ibm.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=dave@stgolabs.net \
--cc=haren@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=kemi.wang@intel.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=will.deacon@arm.com \
--cc=willy@infradead.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).