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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 340B4C6FD20 for ; Tue, 21 Mar 2023 19:41:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229945AbjCUTlX (ORCPT ); Tue, 21 Mar 2023 15:41:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60844 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229484AbjCUTlV (ORCPT ); Tue, 21 Mar 2023 15:41:21 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 62C665371D for ; Tue, 21 Mar 2023 12:40:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1679427549; 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: in-reply-to:in-reply-to:references:references; bh=PkHbf1v/TeW0kF6HmTdS9KScSLUYYXyk622NGMWYMjE=; b=UXywOZpDVcCQqaXDzR+AaSgt3HlxEjYbomNEzvGN4X7/sf4ozlAtLZN5mDi/iW/zADr27X jW5Saxr7zzwWFEVVtI1dDg+3qFrcbdIsde1SUhKI179+r3vgnTe2sUNU+x+V9eU8klKMqr rHMK3Al1aV4sb79uVog0vTi/o/w5oug= Received: from mail-qt1-f200.google.com (mail-qt1-f200.google.com [209.85.160.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-379-AoZ5ew4VOFSxx-8IsDD_SA-1; Tue, 21 Mar 2023 15:35:57 -0400 X-MC-Unique: AoZ5ew4VOFSxx-8IsDD_SA-1 Received: by mail-qt1-f200.google.com with SMTP id u22-20020a05622a011600b003dfd61e8594so4983502qtw.15 for ; Tue, 21 Mar 2023 12:35:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679427356; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=PkHbf1v/TeW0kF6HmTdS9KScSLUYYXyk622NGMWYMjE=; b=4ac45t8X7UBKn5r1qV+IQAeVQfNNWQUroakUtzkXsWFIlFZRkc2xZrtJQiOxh+14jt O6Ko1/Mp6YpYLXMhuj60QVWIjcM3a7Exjhd3lO7h7yo4A5Ev0WqdF4hcIkN/V2X5qcB5 12o8FIZO/8iHIhyPkVCTD2GomCdU65Kqq2t+0frU0Fdp7pYRDbtljOvIByNcSiupNUoX ve1xIOiMHPEnxCq7USRsk9z6pdoz5EqvV5z11N5jrYjVDeNYoAzzRURbAHnZimc6et8A zyeDWZ8Q6TUNRVk83122surI6+jkGy4zMBoaNUCi3Zl77+f+SbWh0faOxczOKLOtRQTX bSRg== X-Gm-Message-State: AO0yUKW6gTN0TiamDnBk3afBNq/9ABmF3ZdeKMvj55+ynab07bIdeLrw wlT++/m9iUIae+uOwagcfVE7XnopPT+RsQMjQmR1awR0pA3PCLrLM8SPtM3p7zNKjjmBg2mmn5O D+IToREZlbMG6FwwFstAFxc1AcgbOvFkc X-Received: by 2002:a05:622a:1a17:b0:3e3:7ed0:d6df with SMTP id f23-20020a05622a1a1700b003e37ed0d6dfmr7146938qtb.6.1679427356673; Tue, 21 Mar 2023 12:35:56 -0700 (PDT) X-Google-Smtp-Source: AK7set/1G9IE3BTdBMPqhFVArq51OpJH8MCFFhHpaUyXIe8c4hd5ykBJuU5X/upf6HakV7unCN1aoQ== X-Received: by 2002:a05:622a:1a17:b0:3e3:7ed0:d6df with SMTP id f23-20020a05622a1a1700b003e37ed0d6dfmr7146908qtb.6.1679427356422; Tue, 21 Mar 2023 12:35:56 -0700 (PDT) Received: from x1n (bras-base-aurron9127w-grc-40-70-52-229-124.dsl.bell.ca. [70.52.229.124]) by smtp.gmail.com with ESMTPSA id 15-20020a05620a048f00b0074636e35405sm2443163qkr.65.2023.03.21.12.35.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 21 Mar 2023 12:35:55 -0700 (PDT) Date: Tue, 21 Mar 2023 15:35:54 -0400 From: Peter Xu To: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Mike Kravetz Cc: Andrea Arcangeli , Andrew Morton , Axel Rasmussen , Mike Rapoport , Nadav Amit , David Hildenbrand , Muhammad Usama Anjum , linux-stable Subject: Re: [PATCH] mm/hugetlb: Fix uffd wr-protection for CoW optimization path Message-ID: References: <20230321191840.1897940-1-peterx@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230321191840.1897940-1-peterx@redhat.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mike, For some reason I forgot to copy you.. sorry. Here's the link: https://lore.kernel.org/linux-mm/20230321191840.1897940-1-peterx@redhat.com On Tue, Mar 21, 2023 at 03:18:40PM -0400, Peter Xu wrote: > This patch fixes an issue that a hugetlb uffd-wr-protected mapping can be > writable even with uffd-wp bit set. It only happens with all these > conditions met: (1) hugetlb memory (2) private mapping (3) original mapping > was missing, then (4) being wr-protected (IOW, pte marker installed). Then > write to the page to trigger. > > Userfaultfd-wp trap for hugetlb was implemented in hugetlb_fault() before > even reaching hugetlb_wp() to avoid taking more locks that userfault won't > need. However there's one CoW optimization path for missing hugetlb page > that can trigger hugetlb_wp() inside hugetlb_no_page(), that can bypass the > userfaultfd-wp traps. > > A few ways to resolve this: > > (1) Skip the CoW optimization for hugetlb private mapping, considering > that private mappings for hugetlb should be very rare, so it may not > really be helpful to major workloads. The worst case is we only skip the > optimization if userfaultfd_wp(vma)==true, because uffd-wp needs another > fault anyway. > > (2) Move the userfaultfd-wp handling for hugetlb from hugetlb_fault() > into hugetlb_wp(). The major cons is there're a bunch of locks taken > when calling hugetlb_wp(), and that will make the changeset unnecessarily > complicated due to the lock operations. > > (3) Carry over uffd-wp bit in hugetlb_wp(), so it'll need to fault again > for uffd-wp privately mapped pages. > > This patch chose option (3) which contains the minimum changeset (simplest > for backport) and also make sure hugetlb_wp() itself will start to be > always safe with uffd-wp ptes even if called elsewhere in the future. > > This patch will be needed for v5.19+ hence copy stable. > > Reported-by: Muhammad Usama Anjum > Cc: linux-stable > Fixes: 166f3ecc0daf ("mm/hugetlb: hook page faults for uffd write protection") > Signed-off-by: Peter Xu > --- > mm/hugetlb.c | 8 +++++--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > diff --git a/mm/hugetlb.c b/mm/hugetlb.c > index 8bfd07f4c143..22337b191eae 100644 > --- a/mm/hugetlb.c > +++ b/mm/hugetlb.c > @@ -5478,7 +5478,7 @@ static vm_fault_t hugetlb_wp(struct mm_struct *mm, struct vm_area_struct *vma, > struct folio *pagecache_folio, spinlock_t *ptl) > { > const bool unshare = flags & FAULT_FLAG_UNSHARE; > - pte_t pte; > + pte_t pte, newpte; > struct hstate *h = hstate_vma(vma); > struct page *old_page; > struct folio *new_folio; > @@ -5622,8 +5622,10 @@ static vm_fault_t hugetlb_wp(struct mm_struct *mm, struct vm_area_struct *vma, > mmu_notifier_invalidate_range(mm, range.start, range.end); > page_remove_rmap(old_page, vma, true); > hugepage_add_new_anon_rmap(new_folio, vma, haddr); > - set_huge_pte_at(mm, haddr, ptep, > - make_huge_pte(vma, &new_folio->page, !unshare)); > + newpte = make_huge_pte(vma, &new_folio->page, !unshare); > + if (huge_pte_uffd_wp(pte)) > + newpte = huge_pte_mkuffd_wp(newpte); > + set_huge_pte_at(mm, haddr, ptep, newpte); > folio_set_hugetlb_migratable(new_folio); > /* Make the old page be freed below */ > new_folio = page_folio(old_page); > -- > 2.39.1 > -- Peter Xu