From patchwork Mon Oct 3 18:38:53 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yang Shi X-Patchwork-Id: 12997743 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id D5863C433FE for ; Mon, 3 Oct 2022 18:39:00 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 5F7BF8E0001; Mon, 3 Oct 2022 14:39:00 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 57FF16B0073; Mon, 3 Oct 2022 14:39:00 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 3AB948E0001; Mon, 3 Oct 2022 14:39:00 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 16A816B0071 for ; Mon, 3 Oct 2022 14:39:00 -0400 (EDT) Received: from smtpin27.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id D0508120C01 for ; Mon, 3 Oct 2022 18:38:59 +0000 (UTC) X-FDA: 79980499998.27.63C011F Received: from mail-pj1-f44.google.com (mail-pj1-f44.google.com [209.85.216.44]) by imf23.hostedemail.com (Postfix) with ESMTP id 55E58140017 for ; Mon, 3 Oct 2022 18:38:58 +0000 (UTC) Received: by mail-pj1-f44.google.com with SMTP id 70so10619087pjo.4 for ; Mon, 03 Oct 2022 11:38:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:to :from:from:to:cc:subject:date; bh=sjZWL20TkiJwGgcx4jgs+B1HCML+Om4Y6HZKNPskHdE=; b=lTEgmLtJAaaW319lD8NxUavIHchOMvenkBspNtdql7goygrt2OecNNIYMulDlbyH+n O8MJHSFArb/mLJtsSbCjOimV1phRuLIfAVqD9c8kpQpyeuyCquuTvpEQ/iaO382f4gMO +n1KlFVL6Wp+aWiH2zfWefBww6orTwt0ovP+wQC3QkI/GlRdDMrXUGmEmfm5V3DhYt5h sGQ9UnLeVt6kzDOfmzmjtmHWAydh1gyY4irm2EOTuXMP1gfU4prKvzQfGF3aq0moytVI ZrNU8xIf4KpFDCZzXGg/qNqLHTaAO9fOakwAEX7qXsTBxt3fFPJJmc0d1RdL594A7K/v Yr+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:to :from:x-gm-message-state:from:to:cc:subject:date; bh=sjZWL20TkiJwGgcx4jgs+B1HCML+Om4Y6HZKNPskHdE=; b=SG10li8sfm74klGe47nFqlpcqng11PD1i6czNDUId9MOjwOTZQJBF/9p+77ynhcL8r FuLQEtS6qemYEbXpBpazPhCeFGy4MSRwytOJIplkghVNo5Kopu6KrudEfuCyVhjfh0PE JhGSqWgzqx5KTILQchp3nOsI3CLDry9rZLiRbrmOYt5Fdc3gay5paf8OLolMVniBavWs pWnV3nS6QrgRGHg3vRtrd0kvUw1WgNWbTY8iXGcPPueeT+hvdFZng9+e5c59JE/1vkmI Vs/mVpFAQTVikWBOsu6FB7zf+OUyhmjUJqBRiruBvEAUtISwLRKp+YX18pSEgTg7gXbf 9w5Q== X-Gm-Message-State: ACrzQf1cT1PncicO3PbwKmxbwVgx7vD0PF9uTU3WGxIdNUKW3/GWCzZq NH/C4gJSeAZtnC+ChYpYAII= X-Google-Smtp-Source: AMsMyM6XKESrS1Zbta0w4U1JcfsK/Avqwpn/WkIEy+bF5c/2xIccCxrr4og6pBowKYFs5kLfd1CFAA== X-Received: by 2002:a17:90b:4c46:b0:202:b9c5:2f24 with SMTP id np6-20020a17090b4c4600b00202b9c52f24mr12892071pjb.180.1664822337344; Mon, 03 Oct 2022 11:38:57 -0700 (PDT) Received: from localhost.localdomain (c-67-174-241-145.hsd1.ca.comcast.net. [67.174.241.145]) by smtp.gmail.com with ESMTPSA id p187-20020a625bc4000000b00537b8deef41sm7692082pfb.136.2022.10.03.11.38.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 03 Oct 2022 11:38:56 -0700 (PDT) From: Yang Shi To: gregkh@linuxfoundation.org, akpm@linux-foundation.org, aneesh.kumar@linux.ibm.com, christophe.leroy@csgroup.eu, david@redhat.com, hughd@google.com, jgg@nvidia.com, jhubbard@nvidia.com, kirill.shutemov@linux.intel.com, mpe@ellerman.id.au, npiggin@gmail.com, peterx@redhat.com, stable@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: [5.15-stable PATCH] mm: gup: fix the fast GUP race against THP collapse Date: Mon, 3 Oct 2022 11:38:53 -0700 Message-Id: <20221003183853.1446126-1-shy828301@gmail.com> X-Mailer: git-send-email 2.26.3 MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1664822338; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references:dkim-signature; bh=sjZWL20TkiJwGgcx4jgs+B1HCML+Om4Y6HZKNPskHdE=; b=r5Fw6MiOYXrm/hb4d2NsAUFRjUkNnXgPm6fYfi5wXbKXyD/3oeOXU1MQv/VVxwKbCxAMu9 38p6yYeFymit6yKyNEXpQsYwYiQlHP8jXpis627yhUkd/D7RwXuR535H6IwTuvpviL4S0/ JTTyjVtlXWMyJf+BIT/zQgTVvb5NBH8= ARC-Authentication-Results: i=1; imf23.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=lTEgmLtJ; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (imf23.hostedemail.com: domain of shy828301@gmail.com designates 209.85.216.44 as permitted sender) smtp.mailfrom=shy828301@gmail.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1664822338; a=rsa-sha256; cv=none; b=TNKHp9G/gXnfsfsKNAumdQvV2BjtXKK9mhiiUWYhdMJhvSHeUDdgLV+m9W6R2BJbuOw2a2 VA2IJ5Dmyu3oM5424LsalnrG+98c0KicHrT49+5L4s1XKtxnZvwsikH5RQghJWptpPHarU 23dSp958O+w19QgEu5L7l11ogwoxgno= X-Rspamd-Queue-Id: 55E58140017 Authentication-Results: imf23.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=lTEgmLtJ; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (imf23.hostedemail.com: domain of shy828301@gmail.com designates 209.85.216.44 as permitted sender) smtp.mailfrom=shy828301@gmail.com X-Rspam-User: X-Rspamd-Server: rspam10 X-Stat-Signature: ziozjnrny773jb8b7m8b7bufwf7az7qw X-HE-Tag: 1664822338-450849 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: commit 70cbc3cc78a997d8247b50389d37c4e1736019da upstream Since general RCU GUP fast was introduced in commit 2667f50e8b81 ("mm: introduce a general RCU get_user_pages_fast()"), a TLB flush is no longer sufficient to handle concurrent GUP-fast in all cases, it only handles traditional IPI-based GUP-fast correctly. On architectures that send an IPI broadcast on TLB flush, it works as expected. But on the architectures that do not use IPI to broadcast TLB flush, it may have the below race: CPU A CPU B THP collapse fast GUP gup_pmd_range() <-- see valid pmd gup_pte_range() <-- work on pte pmdp_collapse_flush() <-- clear pmd and flush __collapse_huge_page_isolate() check page pinned <-- before GUP bump refcount pin the page check PTE <-- no change __collapse_huge_page_copy() copy data to huge page ptep_clear() install huge pmd for the huge page return the stale page discard the stale page The race can be fixed by checking whether PMD is changed or not after taking the page pin in fast GUP, just like what it does for PTE. If the PMD is changed it means there may be parallel THP collapse, so GUP should back off. Also update the stale comment about serializing against fast GUP in khugepaged. Link: https://lkml.kernel.org/r/20220907180144.555485-1-shy828301@gmail.com Fixes: 2667f50e8b81 ("mm: introduce a general RCU get_user_pages_fast()") Acked-by: David Hildenbrand Acked-by: Peter Xu Signed-off-by: Yang Shi Reviewed-by: John Hubbard Cc: "Aneesh Kumar K.V" Cc: Hugh Dickins Cc: Jason Gunthorpe Cc: "Kirill A. Shutemov" Cc: Michael Ellerman Cc: Nicholas Piggin Cc: Christophe Leroy Cc: Signed-off-by: Andrew Morton --- mm/gup.c | 34 ++++++++++++++++++++++++++++------ mm/khugepaged.c | 10 ++++++---- 2 files changed, 34 insertions(+), 10 deletions(-) diff --git a/mm/gup.c b/mm/gup.c index 05068d3d2557..1a23cd0b4fba 100644 --- a/mm/gup.c +++ b/mm/gup.c @@ -2266,8 +2266,28 @@ static void __maybe_unused undo_dev_pagemap(int *nr, int nr_start, } #ifdef CONFIG_ARCH_HAS_PTE_SPECIAL -static int gup_pte_range(pmd_t pmd, unsigned long addr, unsigned long end, - unsigned int flags, struct page **pages, int *nr) +/* + * Fast-gup relies on pte change detection to avoid concurrent pgtable + * operations. + * + * To pin the page, fast-gup needs to do below in order: + * (1) pin the page (by prefetching pte), then (2) check pte not changed. + * + * For the rest of pgtable operations where pgtable updates can be racy + * with fast-gup, we need to do (1) clear pte, then (2) check whether page + * is pinned. + * + * Above will work for all pte-level operations, including THP split. + * + * For THP collapse, it's a bit more complicated because fast-gup may be + * walking a pgtable page that is being freed (pte is still valid but pmd + * can be cleared already). To avoid race in such condition, we need to + * also check pmd here to make sure pmd doesn't change (corresponds to + * pmdp_collapse_flush() in the THP collapse code path). + */ +static int gup_pte_range(pmd_t pmd, pmd_t *pmdp, unsigned long addr, + unsigned long end, unsigned int flags, + struct page **pages, int *nr) { struct dev_pagemap *pgmap = NULL; int nr_start = *nr, ret = 0; @@ -2312,7 +2332,8 @@ static int gup_pte_range(pmd_t pmd, unsigned long addr, unsigned long end, goto pte_unmap; } - if (unlikely(pte_val(pte) != pte_val(*ptep))) { + if (unlikely(pmd_val(pmd) != pmd_val(*pmdp)) || + unlikely(pte_val(pte) != pte_val(*ptep))) { put_compound_head(head, 1, flags); goto pte_unmap; } @@ -2357,8 +2378,9 @@ static int gup_pte_range(pmd_t pmd, unsigned long addr, unsigned long end, * get_user_pages_fast_only implementation that can pin pages. Thus it's still * useful to have gup_huge_pmd even if we can't operate on ptes. */ -static int gup_pte_range(pmd_t pmd, unsigned long addr, unsigned long end, - unsigned int flags, struct page **pages, int *nr) +static int gup_pte_range(pmd_t pmd, pmd_t *pmdp, unsigned long addr, + unsigned long end, unsigned int flags, + struct page **pages, int *nr) { return 0; } @@ -2667,7 +2689,7 @@ static int gup_pmd_range(pud_t *pudp, pud_t pud, unsigned long addr, unsigned lo if (!gup_huge_pd(__hugepd(pmd_val(pmd)), addr, PMD_SHIFT, next, flags, pages, nr)) return 0; - } else if (!gup_pte_range(pmd, addr, next, flags, pages, nr)) + } else if (!gup_pte_range(pmd, pmdp, addr, next, flags, pages, nr)) return 0; } while (pmdp++, addr = next, addr != end); diff --git a/mm/khugepaged.c b/mm/khugepaged.c index 8a8b3aa92937..dd069afd9cb9 100644 --- a/mm/khugepaged.c +++ b/mm/khugepaged.c @@ -1146,10 +1146,12 @@ static void collapse_huge_page(struct mm_struct *mm, pmd_ptl = pmd_lock(mm, pmd); /* probably unnecessary */ /* - * After this gup_fast can't run anymore. This also removes - * any huge TLB entry from the CPU so we won't allow - * huge and small TLB entries for the same virtual address - * to avoid the risk of CPU bugs in that area. + * This removes any huge TLB entry from the CPU so we won't allow + * huge and small TLB entries for the same virtual address to + * avoid the risk of CPU bugs in that area. + * + * Parallel fast GUP is fine since fast GUP will back off when + * it detects PMD is changed. */ _pmd = pmdp_collapse_flush(vma, address, pmd); spin_unlock(pmd_ptl);