Received: by 2002:a05:7412:37c9:b0:e2:908c:2ebd with SMTP id jz9csp2828592rdb; Fri, 22 Sep 2023 09:22:34 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFQMgFDo+OCKFfrq/27FetXLIbi9ezIlp5CDcCfdfXR3XxY+a/9jAJl0goI+IWJE02u+naW X-Received: by 2002:a17:90a:8b91:b0:268:557e:1848 with SMTP id z17-20020a17090a8b9100b00268557e1848mr198190pjn.2.1695399753710; Fri, 22 Sep 2023 09:22:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1695399753; cv=none; d=google.com; s=arc-20160816; b=ZvMnNZ52vymFimEEoSko9MV7K7kgToR5Gl1brJILRfRCUOvJz9J2HkgLf3eIj6LNnc u8gWl17M98647AmXcBauoIusfTNIqGto9XmSe2J793Oss6cltUc0yi4c71+Xkiw/Ygwk PBEPMs2/zURr+CQbVv3fRvaY4d9lQl7J2FGGTDjTKgL3bBAluu4bhTaF4JuvsDWRx8ZO ZH/+OWamxKM9D0asdLFmF5+b0mHntRj2I50xEJkABOIiTpKHBnYBcme6Xisj7gHzEKkA urcjortZoDGzn7P1QUXj/29ugyRxvyPcw1K4oseo/0oqPvXu1uNT6JGgFnw+R3FsCn/W jCOw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=h15BO+2hA5DZuHXtvRUKzXrPKOzsFf08nLHT4NabPc4=; fh=j91obabUFSAHC7B8XLgOvAg9Rfs4u5hpFjNzeGC8sT0=; b=B2OcCFIiXgzk6lHo7KUY0IMo9cT7IrW8xdyICR7RI5Tyz5i7SDDfWHihAcMDMxmyd0 ryPs9CA7YGMfWn0hVeiGgCA8o5XJYs7fsAKfDMpHxXgjQWr6FKK+1PSNJQD0a3TCo2RU 932HGbkcnwKljt2Zuxcgg3v4KPP0zOivcsTdrpHLOda06KS5T0SapMOSN/3EZYxDMyaf 2SikZjK3TSPyH/LXHMdii8JTXDWtTs2BuDRtQi1eQqHmUmUSpChuEY0Eg8Bv8/1ExUyc 68CY6gSZVEwTGUErsJih0JtlNXO4VdHdKCNn/abmpwzSBSeaQUglh3xWhABqOgKXA0Nw 24MA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=r2KQI46M; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from howler.vger.email (howler.vger.email. [2620:137:e000::3:4]) by mx.google.com with ESMTPS id az2-20020a17090b028200b00273fa934cc1si6259248pjb.167.2023.09.22.09.22.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Sep 2023 09:22:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) client-ip=2620:137:e000::3:4; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=r2KQI46M; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by howler.vger.email (Postfix) with ESMTP id AA9AC84C80E8; Fri, 22 Sep 2023 09:14:20 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at howler.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229541AbjIVQOX (ORCPT + 99 others); Fri, 22 Sep 2023 12:14:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52412 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229503AbjIVQOV (ORCPT ); Fri, 22 Sep 2023 12:14:21 -0400 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 13E49102; Fri, 22 Sep 2023 09:14:15 -0700 (PDT) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 52A71C433C7; Fri, 22 Sep 2023 16:14:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1695399254; bh=ghtojmtAqFRtX4PcgZLlC2VPw2Ttv8ZnkZD0uHf6G3Y=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=r2KQI46MuFtdt7QHNa6AqgiJz/M5ENzMW7kPwq5MHDWzFycJ2+pY4u3MqsA9xu0nC W/HNBy22Xw7JneqjviL2IaJu3dGzWLn16NZ5LDkp581LGZMdDZg4052edSPlLkbLHO EwdDs5kw6QxWcMB8DPa5TapO2QHn2N4oQOpAikE02mi4L04UnKYumRRdcwACdUxhgT xMQKjaY0zqYX4QHMGOi217/faMzXeE4+N/6foqQ34cnGlWvVCbUdZdJPU2NbwsyjUC p3AMpsc8yh3FbtfuQO9iVhIkFE9bRCE4VRqafiuyTvaj8qLItH92nbbD52ZVQBMP1Q LphK+HBo/3yDg== Date: Fri, 22 Sep 2023 17:14:04 +0100 From: Will Deacon To: Ryan Roberts Cc: Catalin Marinas , "James E.J. Bottomley" , Helge Deller , Nicholas Piggin , Christophe Leroy , Paul Walmsley , Palmer Dabbelt , Albert Ou , Heiko Carstens , Vasily Gorbik , Alexander Gordeev , Christian Borntraeger , Sven Schnelle , Gerald Schaefer , "David S. Miller" , Arnd Bergmann , Mike Kravetz , Muchun Song , SeongJae Park , Andrew Morton , Uladzislau Rezki , Christoph Hellwig , Lorenzo Stoakes , Anshuman Khandual , Peter Xu , Axel Rasmussen , Qi Zheng , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, sparclinux@vger.kernel.org, linux-mm@kvack.org, stable@vger.kernel.org Subject: Re: [PATCH v2 2/2] arm64: hugetlb: Fix set_huge_pte_at() to work with all swap entries Message-ID: <20230922161404.GA23332@willie-the-truck> References: <20230922115804.2043771-1-ryan.roberts@arm.com> <20230922115804.2043771-3-ryan.roberts@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230922115804.2043771-3-ryan.roberts@arm.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (howler.vger.email [0.0.0.0]); Fri, 22 Sep 2023 09:14:20 -0700 (PDT) On Fri, Sep 22, 2023 at 12:58:04PM +0100, Ryan Roberts wrote: > When called with a swap entry that does not embed a PFN (e.g. > PTE_MARKER_POISONED or PTE_MARKER_UFFD_WP), the previous implementation > of set_huge_pte_at() would either cause a BUG() to fire (if > CONFIG_DEBUG_VM is enabled) or cause a dereference of an invalid address > and subsequent panic. > > arm64's huge pte implementation supports multiple huge page sizes, some > of which are implemented in the page table with multiple contiguous > entries. So set_huge_pte_at() needs to work out how big the logical pte > is, so that it can also work out how many physical ptes (or pmds) need > to be written. It previously did this by grabbing the folio out of the > pte and querying its size. > > However, there are cases when the pte being set is actually a swap > entry. But this also used to work fine, because for huge ptes, we only > ever saw migration entries and hwpoison entries. And both of these types > of swap entries have a PFN embedded, so the code would grab that and > everything still worked out. > > But over time, more calls to set_huge_pte_at() have been added that set > swap entry types that do not embed a PFN. And this causes the code to go > bang. The triggering case is for the uffd poison test, commit > 99aa77215ad0 ("selftests/mm: add uffd unit test for UFFDIO_POISON"), > which causes a PTE_MARKER_POISONED swap entry to be set, coutesey of > commit 8a13897fb0da ("mm: userfaultfd: support UFFDIO_POISON for > hugetlbfs") - added in v6.5-rc7. Although review shows that there are > other call sites that set PTE_MARKER_UFFD_WP (which also has no PFN), > these don't trigger on arm64 because arm64 doesn't support UFFD WP. > > Arguably, the root cause is really due to commit 18f3962953e4 ("mm: > hugetlb: kill set_huge_swap_pte_at()"), which aimed to simplify the > interface to the core code by removing set_huge_swap_pte_at() (which > took a page size parameter) and replacing it with calls to > set_huge_pte_at() where the size was inferred from the folio, as > descibed above. While that commit didn't break anything at the time, it > did break the interface because it couldn't handle swap entries without > PFNs. And since then new callers have come along which rely on this > working. But given the brokeness is only observable after commit > 8a13897fb0da ("mm: userfaultfd: support UFFDIO_POISON for hugetlbfs"), > that one gets the Fixes tag. > > Now that we have modified the set_huge_pte_at() interface to pass the > huge page size in the previous patch, we can trivially fix this issue. > > Signed-off-by: Ryan Roberts > Fixes: 8a13897fb0da ("mm: userfaultfd: support UFFDIO_POISON for hugetlbfs") > Cc: # 6.5+ > --- > arch/arm64/mm/hugetlbpage.c | 17 +++-------------- > 1 file changed, 3 insertions(+), 14 deletions(-) > > diff --git a/arch/arm64/mm/hugetlbpage.c b/arch/arm64/mm/hugetlbpage.c > index a7f8c8db3425..13fd592228b1 100644 > --- a/arch/arm64/mm/hugetlbpage.c > +++ b/arch/arm64/mm/hugetlbpage.c > @@ -241,13 +241,6 @@ static void clear_flush(struct mm_struct *mm, > flush_tlb_range(&vma, saddr, addr); > } > > -static inline struct folio *hugetlb_swap_entry_to_folio(swp_entry_t entry) > -{ > - VM_BUG_ON(!is_migration_entry(entry) && !is_hwpoison_entry(entry)); > - > - return page_folio(pfn_to_page(swp_offset_pfn(entry))); > -} > - > void set_huge_pte_at(struct mm_struct *mm, unsigned long addr, > pte_t *ptep, pte_t pte, unsigned long sz) > { > @@ -257,13 +250,10 @@ void set_huge_pte_at(struct mm_struct *mm, unsigned long addr, > unsigned long pfn, dpfn; > pgprot_t hugeprot; > > - if (!pte_present(pte)) { > - struct folio *folio; > - > - folio = hugetlb_swap_entry_to_folio(pte_to_swp_entry(pte)); > - ncontig = num_contig_ptes(folio_size(folio), &pgsize); > + ncontig = num_contig_ptes(sz, &pgsize); > > - for (i = 0; i < ncontig; i++, ptep++) > + if (!pte_present(pte)) { > + for (i = 0; i < ncontig; i++, ptep++, addr += pgsize) > set_pte_at(mm, addr, ptep, pte); Our set_pte_at() doesn't use 'addr' for anything and the old code didn't even bother to increment it here! I'm fine adding that, but it feels unrelated to the issue which this patch is actually fixing. Either way: Acked-by: Will Deacon Will