From patchwork Mon Oct 3 15:56:28 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Peter Xu X-Patchwork-Id: 12997650 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 28A07C4332F for ; Mon, 3 Oct 2022 15:56:38 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 78EA96B0071; Mon, 3 Oct 2022 11:56:37 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 716E48E0003; Mon, 3 Oct 2022 11:56:37 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 56A6B8E0002; Mon, 3 Oct 2022 11:56:37 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 3004D6B0071 for ; Mon, 3 Oct 2022 11:56:37 -0400 (EDT) Received: from smtpin24.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id E3965140803 for ; Mon, 3 Oct 2022 15:56:36 +0000 (UTC) X-FDA: 79980090792.24.B4F68E8 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by imf30.hostedemail.com (Postfix) with ESMTP id 659B38001D for ; Mon, 3 Oct 2022 15:56:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664812595; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=EmARIE0aFvhZ3doTDEW0tn2T6UXUcOfWmNkW2tjznSw=; b=bHUvrTaCsrCImN1jcOX/ElPYpDtMuerBYvo9iNqRbT68Oxp1SBRqW7SMNy9KlwVqomeJJ0 SfUfd/OXoUfAk8K2imxgcSnGXPuI/ogfXc+8S2jJvLwZrjUYEMJ8+wMtH06BD66C/DPV8G 2Bdwe1mneRzpVgT9l6tRL9Z4wMUDH4E= Received: from mail-qv1-f69.google.com (mail-qv1-f69.google.com [209.85.219.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-365-TpFn50XwP1O35i8w_sTsjg-1; Mon, 03 Oct 2022 11:56:34 -0400 X-MC-Unique: TpFn50XwP1O35i8w_sTsjg-1 Received: by mail-qv1-f69.google.com with SMTP id ks15-20020a056214310f00b004b18ea4bc05so1621466qvb.22 for ; Mon, 03 Oct 2022 08:56:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date; bh=EmARIE0aFvhZ3doTDEW0tn2T6UXUcOfWmNkW2tjznSw=; b=JUSUUFmIHvVoMiSMxFUdOjNDXJxq2wMSKaKTSw4DX/EijWwCz4cJbGKG68WzcMce+J e1XYJUzAOPNXqIXWuNymwyuXP0Zy5vnXAOcYc9+75Xn/p8V7gzZvYFB3+IF8eK0/APpb B4P8p4vxOhxDtKfpGE0fT0DgcKEwb/g7AbY1KiPKMKeHXWp+nkrnwc/YYPftaqnxiqY3 CVQk3oBMaHJtfJV8oAHVXduVvuHLk4I9B4zDotmlyqMUQtQapBVIVJUcY1MxJv7c13xw WFP37JFLzgeoYn08tEovsU7R+2H9AM4+PBLBVqiX4FMjuN7br8TbkOtLamwWbNn64Cd2 0K2g== X-Gm-Message-State: ACrzQf1xsOeCSx4mpKq3gyydzW/tcUAS2GUVbie8e1cJejsA67z1oiMl SLaUP6epj5rjxSmfWFJeZQuGpUMbjHqgQAVbhIm0+N2z5ssUdXJtKXOmkal6ec6yB/3XqeHs9LE yG9h5VILgU9E= X-Received: by 2002:a05:6214:2386:b0:4af:9757:81bd with SMTP id fw6-20020a056214238600b004af975781bdmr16584734qvb.124.1664812594148; Mon, 03 Oct 2022 08:56:34 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7i9AD0amdQk3NjDYMMsoIIttZ30lWkBTlVS+OXE/Wk+5ArMOHq16CUgv3zbMNLCWQAhaWK0Q== X-Received: by 2002:a05:6214:2386:b0:4af:9757:81bd with SMTP id fw6-20020a056214238600b004af975781bdmr16584720qvb.124.1664812593972; Mon, 03 Oct 2022 08:56:33 -0700 (PDT) Received: from x1n.redhat.com (bras-base-aurron9127w-grc-46-70-31-27-79.dsl.bell.ca. [70.31.27.79]) by smtp.gmail.com with ESMTPSA id bs18-20020a05620a471200b006cf38fd659asm10956732qkb.103.2022.10.03.08.56.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 03 Oct 2022 08:56:33 -0700 (PDT) From: Peter Xu To: linux-kernel@vger.kernel.org, linux-mm@kvack.org Cc: peterx@redhat.com, Andrea Arcangeli , Mike Rapoport , David Hildenbrand , Andrew Morton , Axel Rasmussen , Mike Kravetz , Nadav Amit Subject: [PATCH 1/3] mm/hugetlb: Fix race condition of uffd missing/minor handling Date: Mon, 3 Oct 2022 11:56:28 -0400 Message-Id: <20221003155630.469263-2-peterx@redhat.com> X-Mailer: git-send-email 2.37.3 In-Reply-To: <20221003155630.469263-1-peterx@redhat.com> References: <20221003155630.469263-1-peterx@redhat.com> MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-type: text/plain ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1664812596; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=EmARIE0aFvhZ3doTDEW0tn2T6UXUcOfWmNkW2tjznSw=; b=BlTRUA/BJ9RIqrQiqLymmQAHltOQhl6usquoh1R4Ue2/jkBeIIp3hDU+uJb80aZkjTUKL7 p3B4FMRUuiappQboTxK34wFO5hk3FMYUUHdpiAtOf6638gGhW5YnUeLpfjO7oLCBe7HOZl dhuHJnALdkesfxgOWSWOA/ZgM+ExrTs= ARC-Authentication-Results: i=1; imf30.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=bHUvrTaC; dmarc=pass (policy=none) header.from=redhat.com; spf=pass (imf30.hostedemail.com: domain of peterx@redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=peterx@redhat.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1664812596; a=rsa-sha256; cv=none; b=n6i1Zok0oEb9ldzduPzHqaeQ2v6gVUmmmgzwPg7u5iw2fN0w9h40lEFv3lkh+uzZ5jGiNJ T+tjBxshK8TWIrpIG5Xmj9GELXoXmNXGN2doFztYFL4A+BnbDqR9ja9QWiaik+Nu6SsjKg ydX47PPU0xi4SKKxGDKyPR3H0xp82HQ= X-Stat-Signature: qfa43dbkuby1io19i95czdo9bywacrqq X-Rspam-User: X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 659B38001D Authentication-Results: imf30.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=bHUvrTaC; dmarc=pass (policy=none) header.from=redhat.com; spf=pass (imf30.hostedemail.com: domain of peterx@redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=peterx@redhat.com X-HE-Tag: 1664812596-367012 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: After the recent rework patchset of hugetlb locking on pmd sharing, kselftest for userfaultfd sometimes fails on hugetlb private tests with unexpected write fault checks. It turns out there's nothing wrong within the locking series regarding this matter, but it could have changed the timing of threads so it can trigger an old bug. The real bug is when we call hugetlb_no_page() we're not with the pgtable lock. It means we're reading the pte values lockless. It's perfectly fine in most cases because before we do normal page allocations we'll take the lock and check pte_same() again. However before that, there are actually two paths on userfaultfd missing/minor handling that may directly move on with the fault process without checking the pte values. It means for these two paths we may be generating an uffd message based on an unstable pte, while an unstable pte can legally be anything as long as the modifier holds the pgtable lock. One example, which is also what happened in the failing kselftest and caused the test failure, is that for private mappings CoW can happen on one page. CoW requires pte being cleared before being replaced with a new page for TLB coherency, but then there can be a race condition: thread 1 thread 2 -------- -------- hugetlb_fault hugetlb_fault private pte RO hugetlb_wp pgtable_lock() huge_ptep_clear_flush pte=NULL hugetlb_no_page generate uffd missing event even if page existed!! set_huge_pte_at pgtable_unlock() Fix this by recheck the pte after pgtable lock for both userfaultfd missing & minor fault paths. This bug should have been around starting from uffd hugetlb introduced, so attaching a Fixes to the commit. Also attach another Fixes to the minor support commit for easier tracking. Note that userfaultfd is actually fine with false positives (e.g. caused by pte changed), but not wrong logical events (e.g. caused by reading a pte during changing). The latter can confuse the userspace, so the strictness is very much preferred. E.g., MISSING event should never happen on the page after UFFDIO_COPY has correctly installed the page and returned. Cc: Andrea Arcangeli Cc: Mike Kravetz Cc: Axel Rasmussen Cc: Nadav Amit Fixes: 1a1aad8a9b7b ("userfaultfd: hugetlbfs: add userfaultfd hugetlb hook") Fixes: 7677f7fd8be7 ("userfaultfd: add minor fault registration mode") Co-developed-by: Mike Kravetz Signed-off-by: Peter Xu --- mm/hugetlb.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 49 insertions(+), 6 deletions(-) diff --git a/mm/hugetlb.c b/mm/hugetlb.c index 9679fe519b90..fa3fcdb0c4b8 100644 --- a/mm/hugetlb.c +++ b/mm/hugetlb.c @@ -5521,6 +5521,23 @@ static inline vm_fault_t hugetlb_handle_userfault(struct vm_area_struct *vma, return ret; } +/* + * Recheck pte with pgtable lock. Returns true if pte didn't change, or + * false if pte changed or is changing. + */ +static bool hugetlb_pte_stable(struct hstate *h, struct mm_struct *mm, + pte_t *ptep, pte_t old_pte) +{ + spinlock_t *ptl; + bool same; + + ptl = huge_pte_lock(h, mm, ptep); + same = pte_same(huge_ptep_get(ptep), old_pte); + spin_unlock(ptl); + + return same; +} + static vm_fault_t hugetlb_no_page(struct mm_struct *mm, struct vm_area_struct *vma, struct address_space *mapping, pgoff_t idx, @@ -5562,9 +5579,30 @@ static vm_fault_t hugetlb_no_page(struct mm_struct *mm, goto out; /* Check for page in userfault range */ if (userfaultfd_missing(vma)) { - ret = hugetlb_handle_userfault(vma, mapping, idx, - flags, haddr, address, - VM_UFFD_MISSING); + /* + * Since hugetlb_no_page() was examining pte + * without pgtable lock, we need to re-test under + * lock because the pte may not be stable and could + * have changed from under us. Try to detect + * either changed or during-changing ptes and retry + * properly when needed. + * + * Note that userfaultfd is actually fine with + * false positives (e.g. caused by pte changed), + * but not wrong logical events (e.g. caused by + * reading a pte during changing). The latter can + * confuse the userspace, so the strictness is very + * much preferred. E.g., MISSING event should + * never happen on the page after UFFDIO_COPY has + * correctly installed the page and returned. + */ + if (hugetlb_pte_stable(h, mm, ptep, old_pte)) + ret = hugetlb_handle_userfault( + vma, mapping, idx, flags, haddr, + address, VM_UFFD_MISSING); + else + /* Retry the fault */ + ret = 0; goto out; } @@ -5634,9 +5672,14 @@ static vm_fault_t hugetlb_no_page(struct mm_struct *mm, if (userfaultfd_minor(vma)) { unlock_page(page); put_page(page); - ret = hugetlb_handle_userfault(vma, mapping, idx, - flags, haddr, address, - VM_UFFD_MINOR); + /* See comment in userfaultfd_missing() block above */ + if (hugetlb_pte_stable(h, mm, ptep, old_pte)) + ret = hugetlb_handle_userfault( + vma, mapping, idx, flags, haddr, + address, VM_UFFD_MINOR); + else + /* Retry the fault */ + ret = 0; goto out; } }