Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752540AbdGFNrI (ORCPT ); Thu, 6 Jul 2017 09:47:08 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:41085 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752010AbdGFNrH (ORCPT ); Thu, 6 Jul 2017 09:47:07 -0400 Subject: Re: [RFC v5 09/11] mm: Try spin lock in speculative path To: Peter Zijlstra Cc: paulmck@linux.vnet.ibm.com, akpm@linux-foundation.org, kirill@shutemov.name, ak@linux.intel.com, mhocko@kernel.org, dave@stgolabs.net, jack@suse.cz, Matthew Wilcox , 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 References: <1497635555-25679-1-git-send-email-ldufour@linux.vnet.ibm.com> <1497635555-25679-10-git-send-email-ldufour@linux.vnet.ibm.com> <20170705185023.xlqko7wgepwsny5g@hirez.programming.kicks-ass.net> From: Laurent Dufour Date: Thu, 6 Jul 2017 15:46:59 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170705185023.xlqko7wgepwsny5g@hirez.programming.kicks-ass.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 17070613-0040-0000-0000-000003BD65E7 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17070613-0041-0000-0000-000025B7D296 Message-Id: <3af22f3b-03ab-1d37-b2b1-b616adde7eb6@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-07-06_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1707060237 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1455 Lines: 45 On 05/07/2017 20:50, Peter Zijlstra wrote: > On Fri, Jun 16, 2017 at 07:52:33PM +0200, Laurent Dufour wrote: >> @@ -2294,8 +2295,19 @@ static bool pte_map_lock(struct vm_fault *vmf) >> if (vma_has_changed(vmf->vma, vmf->sequence)) >> 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 > > comment style.. Hi Peter and thanks for your work and review. I'll fix this comment style. > >> + * 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->vma, vmf->sequence)) { >> pte_unmap_unlock(pte, ptl); >> goto out; > > Right, so if you look at my earlier patches you'll see I did something > quite disgusting here. > > Not sure that wants repeating, but I cannot remember why I thought this > deadlock didn't exist anymore. Regarding the deadlock I did face it on my Power victim node, so I guess it is still there, and the stack traces are quiet explicit. Am I missing something here ? Thanks, Laurent.