Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp2242443ybb; Sat, 21 Mar 2020 16:46:48 -0700 (PDT) X-Google-Smtp-Source: ADFU+vsQI4bYvgR0ftfcxCn0ZsF857nzXkJ8hikXUd2OKzNOQlU/++TYCoBAqZDTTi5FbwWEb5fj X-Received: by 2002:a05:6830:1ad4:: with SMTP id r20mr12980225otc.316.1584834408248; Sat, 21 Mar 2020 16:46:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584834408; cv=none; d=google.com; s=arc-20160816; b=BJCDnzRdjQWNZjbSU8faeytYEH/uYYDM0GhVG0+8Klu7RQKF2VIhkWN20nuot2vV4G 2Of67+6oqZFcxydRZmfr5ezOxHws4rmkJrVDNy4THKwzriPR5ArmSI6s21JpRBrw65gz YVMkpBfK5HDSOpTEbSHXxua3s11yKgvHpWU9ddyMJGVK22ig8U8us7jQpukXoBB2iNvP XFYPHYPC0x3I/jLdXhcaTTDegGgDp/XqxBqneqAzRsNMIlGtPOax/Vd3MFK5/rJ/AY0p /vsuGcPEWI/QEghmlpfinyuQHMDbOMFFLLZO+UoUuwHlr82j2PHgWL6/xi9qgCPOdrVq BQ7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=EbJlVkcnrCb7yZmR4s7FZM+TlFXShwm0HDQfazo5ftU=; b=MGTSqB7B2KwY9BCoDBkrr6rWzCaMpy3LhwSh0QJ7OzRNDhwa52fbui+Gs2ZdAqghjp FTwy5DWcMQ69iC/Cm2l4Ivu3O+DlhXJsHLz+kKZc/3/+4/ZX75eJSfCPT8zNnTrvOox5 6CZrS0OaZdm+bNSg4qAR23MywGJOOr1xkDvMw2nsbvB3R1KXkoM/mR0zYulPWNWZ2mvx AroyCmbZfjVg6o3TBUunCIUHVE250OTIVn6Dy2b76EbozFNfLRfG1M5UJv3xPJ4Hcjfp HyDe8MRhit3eEo2hK/U/yvkAFAcqrg+wYdhcoeJyPRGLe5eAm4TShYvSEReGCmcrB2Wp xghw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@oracle.com header.s=corp-2020-01-29 header.b=nEoM0Mc7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=oracle.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m11si5450934otq.279.2020.03.21.16.45.59; Sat, 21 Mar 2020 16:46:48 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@oracle.com header.s=corp-2020-01-29 header.b=nEoM0Mc7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=oracle.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728178AbgCUXlC (ORCPT + 99 others); Sat, 21 Mar 2020 19:41:02 -0400 Received: from aserp2120.oracle.com ([141.146.126.78]:41088 "EHLO aserp2120.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728056AbgCUXlB (ORCPT ); Sat, 21 Mar 2020 19:41:01 -0400 Received: from pps.filterd (aserp2120.oracle.com [127.0.0.1]) by aserp2120.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 02LNd1Nt130701; Sat, 21 Mar 2020 23:40:25 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=subject : to : cc : references : from : message-id : date : mime-version : in-reply-to : content-type : content-transfer-encoding; s=corp-2020-01-29; bh=EbJlVkcnrCb7yZmR4s7FZM+TlFXShwm0HDQfazo5ftU=; b=nEoM0Mc7p9J9pof0d2NGAHaQmsXy/+haFkITz0TioE8DfiucztNMFJYX0Cx6jaICQubu IqptRAYcYkyB4BJWJghei+4+WYIe+Yn7H/nSWilK7Nzd1tpS3pf8SPIY7ykbvusru6O1 TWUtU3sstB/5oHc4gMZ+UA8TpHr/VSP96ip3TnxncGCypa9T03f1vQQITUn6SJ+WZvc8 rBBavsTgJ479p28izJA7FsiA1RS00SbSxnSBpANPhNCzkhHGHS/aHpdgQdHHBUxrL/nC IHzrPpujjgC12L2bSDac4SnKIX88KitJnstPvl3xErxusP7f2HwHK12sxMQQS0J1DNpA qA== Received: from userp3030.oracle.com (userp3030.oracle.com [156.151.31.80]) by aserp2120.oracle.com with ESMTP id 2ywavksqja-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 21 Mar 2020 23:40:25 +0000 Received: from pps.filterd (userp3030.oracle.com [127.0.0.1]) by userp3030.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 02LNQnfW003312; Sat, 21 Mar 2020 23:38:24 GMT Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userp3030.oracle.com with ESMTP id 2ywvd98wj0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 21 Mar 2020 23:38:24 +0000 Received: from abhmp0009.oracle.com (abhmp0009.oracle.com [141.146.116.15]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id 02LNcLL7006924; Sat, 21 Mar 2020 23:38:22 GMT Received: from [192.168.1.206] (/71.63.128.209) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 21 Mar 2020 16:38:21 -0700 Subject: Re: [PATCH v2] mm/hugetlb: fix a addressing exception caused by huge_pte_offset() To: "Longpeng (Mike)" , akpm@linux-foundation.org Cc: kirill.shutemov@linux.intel.com, linux-kernel@vger.kernel.org, arei.gonglei@huawei.com, weidong.huang@huawei.com, weifuqiang@huawei.com, kvm@vger.kernel.org, linux-mm@kvack.org, Matthew Wilcox , Sean Christopherson , stable@vger.kernel.org References: <1582342427-230392-1-git-send-email-longpeng2@huawei.com> From: Mike Kravetz Message-ID: <51a25d55-de49-4c0a-c994-bf1a8cfc8638@oracle.com> Date: Sat, 21 Mar 2020 16:38:19 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <1582342427-230392-1-git-send-email-longpeng2@huawei.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9567 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=999 bulkscore=0 spamscore=0 suspectscore=0 mlxscore=0 phishscore=0 adultscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2003210141 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9567 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 malwarescore=0 priorityscore=1501 mlxscore=0 bulkscore=0 clxscore=1011 impostorscore=0 phishscore=0 suspectscore=0 mlxlogscore=999 spamscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2003210141 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/21/20 7:33 PM, Longpeng(Mike) wrote: > From: Longpeng > > Our machine encountered a panic(addressing exception) after run > for a long time and the calltrace is: > RIP: 0010:[] [] hugetlb_fault+0x307/0xbe0 > RSP: 0018:ffff9567fc27f808 EFLAGS: 00010286 > RAX: e800c03ff1258d48 RBX: ffffd3bb003b69c0 RCX: e800c03ff1258d48 > RDX: 17ff3fc00eda72b7 RSI: 00003ffffffff000 RDI: e800c03ff1258d48 > RBP: ffff9567fc27f8c8 R08: e800c03ff1258d48 R09: 0000000000000080 > R10: ffffaba0704c22a8 R11: 0000000000000001 R12: ffff95c87b4b60d8 > R13: 00005fff00000000 R14: 0000000000000000 R15: ffff9567face8074 > FS: 00007fe2d9ffb700(0000) GS:ffff956900e40000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: ffffd3bb003b69c0 CR3: 000000be67374000 CR4: 00000000003627e0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > Call Trace: > [] ? unlock_page+0x2b/0x30 > [] ? hugetlb_fault+0x222/0xbe0 > [] follow_hugetlb_page+0x175/0x540 > [] ? cpumask_next_and+0x35/0x50 > [] __get_user_pages+0x2a0/0x7e0 > [] __get_user_pages_unlocked+0x15d/0x210 > [] __gfn_to_pfn_memslot+0x3c5/0x460 [kvm] > [] try_async_pf+0x6e/0x2a0 [kvm] > [] tdp_page_fault+0x151/0x2d0 [kvm] > [] ? vmx_vcpu_run+0x2ec/0xc80 [kvm_intel] > [] ? vmx_vcpu_run+0x2f8/0xc80 [kvm_intel] > [] kvm_mmu_page_fault+0x31/0x140 [kvm] > [] handle_ept_violation+0x9e/0x170 [kvm_intel] > [] vmx_handle_exit+0x2bc/0xc70 [kvm_intel] > [] ? __vmx_complete_interrupts.part.73+0x80/0xd0 [kvm_intel] > [] ? vmx_vcpu_run+0x490/0xc80 [kvm_intel] > [] vcpu_enter_guest+0x7be/0x13a0 [kvm] > [] ? kvm_check_async_pf_completion+0x8e/0xb0 [kvm] > [] kvm_arch_vcpu_ioctl_run+0x330/0x490 [kvm] > [] kvm_vcpu_ioctl+0x309/0x6d0 [kvm] > [] ? dequeue_signal+0x32/0x180 > [] ? do_sigtimedwait+0xcd/0x230 > [] do_vfs_ioctl+0x3f0/0x540 > [] SyS_ioctl+0xa1/0xc0 > [] system_call_fastpath+0x22/0x27 > > ( The kernel we used is older, but we think the latest kernel also has this > bug after dig into this problem. ) > > For 1G hugepages, huge_pte_offset() wants to return NULL or pudp, but it > may return a wrong 'pmdp' if there is a race. Please look at the following > code snippet: > ... > pud = pud_offset(p4d, addr); > if (sz != PUD_SIZE && pud_none(*pud)) > return NULL; > /* hugepage or swap? */ > if (pud_huge(*pud) || !pud_present(*pud)) > return (pte_t *)pud; > > pmd = pmd_offset(pud, addr); > if (sz != PMD_SIZE && pmd_none(*pmd)) > return NULL; > /* hugepage or swap? */ > if (pmd_huge(*pmd) || !pmd_present(*pmd)) > return (pte_t *)pmd; > ... > > The following sequence would trigger this bug: > 1. CPU0: sz = PUD_SIZE and *pud = 0 , continue > 1. CPU0: "pud_huge(*pud)" is false > 2. CPU1: calling hugetlb_no_page and set *pud to xxxx8e7(PRESENT) > 3. CPU0: "!pud_present(*pud)" is false, continue > 4. CPU0: pmd = pmd_offset(pud, addr) and maybe return a wrong pmdp > However, we want CPU0 to return NULL or pudp. > > We can avoid this race by read the pud only once. What's more, we also use > READ_ONCE to access the entries for safe(e.g. avoid the compilier mischief) > > Cc: Matthew Wilcox > Cc: Sean Christopherson > Cc: Mike Kravetz > Cc: stable@vger.kernel.org > Signed-off-by: Longpeng Andrew dropped this patch from his tree which caused me to go back and look at the status of this patch/issue. It is pretty obvious that code in the current huge_pte_offset routine is racy. I checked out the assembly code produced by my compiler and verified that the line, if (pud_huge(*pud) || !pud_present(*pud)) does actually dereference *pud twice. So, the value could change between those two dereferences. Longpeng (Mike) could easlily recreate the issue if he put a delay between the two dereferences. I believe the only reservations/concerns about the patch below was the use of READ_ONCE(). Is that correct? Are there any objections to the patch if the READ_ONCE() calls are removed? Longpeng (Mike), can you recreate the issue by adding the delay and removing the READ_ONCE() calls? -- Mike Kravetz > --- > v1 -> v2: > - avoid renaming [Matthew, Mike] > > --- > mm/hugetlb.c | 18 ++++++++++-------- > 1 file changed, 10 insertions(+), 8 deletions(-) > > diff --git a/mm/hugetlb.c b/mm/hugetlb.c > index dd8737a..90daf37 100644 > --- a/mm/hugetlb.c > +++ b/mm/hugetlb.c > @@ -4910,28 +4910,30 @@ pte_t *huge_pte_offset(struct mm_struct *mm, > { > pgd_t *pgd; > p4d_t *p4d; > - pud_t *pud; > - pmd_t *pmd; > + pud_t *pud, pud_entry; > + pmd_t *pmd, pmd_entry; > > pgd = pgd_offset(mm, addr); > - if (!pgd_present(*pgd)) > + if (!pgd_present(READ_ONCE(*pgd))) > return NULL; > p4d = p4d_offset(pgd, addr); > - if (!p4d_present(*p4d)) > + if (!p4d_present(READ_ONCE(*p4d))) > return NULL; > > pud = pud_offset(p4d, addr); > - if (sz != PUD_SIZE && pud_none(*pud)) > + pud_entry = READ_ONCE(*pud); > + if (sz != PUD_SIZE && pud_none(pud_entry)) > return NULL; > /* hugepage or swap? */ > - if (pud_huge(*pud) || !pud_present(*pud)) > + if (pud_huge(pud_entry) || !pud_present(pud_entry)) > return (pte_t *)pud; > > pmd = pmd_offset(pud, addr); > - if (sz != PMD_SIZE && pmd_none(*pmd)) > + pmd_entry = READ_ONCE(*pmd); > + if (sz != PMD_SIZE && pmd_none(pmd_entry)) > return NULL; > /* hugepage or swap? */ > - if (pmd_huge(*pmd) || !pmd_present(*pmd)) > + if (pmd_huge(pmd_entry) || !pmd_present(pmd_entry)) > return (pte_t *)pmd; > > return NULL; >