From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794633279; b=DYK1z8ZL5G61Lh4SJ0VKuIZsbVv7s1OXiNvwSMQK7I1HHONF3rBWZQIlBzg6BZ2BBQT5 dBRr5rwmPVI2EfIeCekVTzNTi23x5/G7UcLhJySVfQHICYs8RtU64zv4qeifEhvxSgxvF UyZ5wvkX8OibX/k2hyLZPpGsvivPc9uTum50QuCO/7J1ReI5O6bfnTY2Y2VJ3/9lKMTkp Q/7tD68w6v+MC6JsBC798dRBE3jOmL/X9jyAdZdMDLJSpbCyGbpnc61E0N2+otcsqWeU6 dedMQ3Kyg4tOxFrV1KBiGJnlRKGZX2m7X9Ms9YMm8/8NwKm4p6gd18UY4C+aBLErRJQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794633279; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: In-Reply-To:References:MIME-Version:Content-Transfer-Encoding; bh=bkdaUtkfAwi01ixqtPP0rRxBUSrJXBPQImPYo9tqU7Q=; b=4+u2X3REDzH/m1dRQZ1rA2FYGGBXjpUguAb0KAdcS7SGxlEfXcifjU7h93u4dbjW1B8r jWEYsymGfya5FmlLW7rf7i8N6F7o51bhIiIWagHyWYPQslThcIjeg9ZieUZ7BMmjJo+H+ /1QvplQzzECzZUWCukWeMjMJ8eKjdvl2dWRpInnXm95TazDyoqJqwm3lt3r3ihMfaBeGu rCcROcCsVApFROYNjCMi1wkAy4VWzG3j6o5yEDxwTvhdiV5Ex0qV0oL1qFbeqMRHiZ+m6 gn+AV2wM1RpipXsy5c8U5dTsqUwzCIxkQouwxQ71Sd947l6EiNSDKegWzqI40K8AFaQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=km4flXfS; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9DBFE606A338 for ; Sat, 14 Nov 2026 05:14:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=km4flXfS Received: by smtp.kernel.org (Postfix) with ESMTPSA id 708241F000C4; Sat, 14 Nov 2026 05:14:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1794633279; bh=bkdaUtkfAwi01ixqtPP0rRxBUSrJXBPQImPYo9tqU7Q=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=km4flXfSwcI98mpj0AjYp8WAqgspAh1vcMnlnZZawOvq2HIthmBD0cvpDtFMANEvr CNOmMd7e0iUcI0B7cnp7okEk0JU5jzwEoZN4Lw8EqUKfIHFeA1VX5208MxDHHPD/AZ D0+S+e2cKTXrF5/e+QmfD33UkQoKIZji2Fpi16v+Qjw1sqtC2Jch69f/yzFA+32eFZ 4IbiFaKzOa2g1Fm7wLLVIHFX7tvLesHVXrUh4QG+e3r9O6NZvnq/8PwqLGdtoTk+zr kVfEHqSgXCgSbNeilIK4Zqnh0tGiTZfamnxtqG24Qp15C/knO9YutLw9n1siFvfqUc gfN97uZJ5+mIA== From: Sasha Levin To: stable@vger.kernel.org Cc: "David Hildenbrand (Arm)" , Andrew Morton , Kyle Zeng , "Lorenzo Stoakes (ARM)" , "Kiryl Shutsemau (Meta)" , Baolin Wang , Lance Yang , Barry Song , "Liam R. Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , Ying Huang , Ryan Roberts , Chuanhua Han , Sasha Levin Subject: [PATCH 6.12.y 3/3] mm: fix address wraparound when scanning large folio PTEs Date: Sat, 14 Nov 2026 00:14:33 -0500 Message-ID: <20261114051414.3056118-3-sashal@kernel.org> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20261114051414.3056118-1-sashal@kernel.org> References: <20261109200745-failed-6.12-f681d4580d5c@kernel.org> <20261114051414.3056118-1-sashal@kernel.org> X-Mailing-List: stable@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "David Hildenbrand (Arm)" [ Upstream commit f681d4580d5c3c749f623cda722a21aefd3147b3 ] numa_rebuild_large_mapping() and do_swap_page() can be tricked into generating an address wraparound, crashing the kernel. All that's required is to map a tail page of a large folio close enough to the start/end of the address space to e.g., make unsigned long addr_start = addr - (nr << PAGE_SHIFT); to wrap around. Let's fix it by providing a better helper, folio_scan_range(), that takes care of staying within VMA and page table boundaries while handling possible wraparounds. There are some nasty details, like not being able to use pmd_addr_end() in this context. Add some helpful comments for these cases. Link: https://lore.kernel.org/20261014-folio_pte_scan_range-v2-1-00cf9bbaa364@kernel.org Fixes: d2136d749d76 ("mm: support multi-size THP numa balancing") Fixes: 508758960b8d ("mm: swap: entirely map large folios found in swapcache") Signed-off-by: David Hildenbrand (Arm) Signed-off-by: Andrew Morton Reported-by: Kyle Zeng Reviewed-by: Lorenzo Stoakes (ARM) Reviewed-by: Kiryl Shutsemau (Meta) Reviewed-by: Baolin Wang Reviewed-by: Lance Yang Reviewed-by: Barry Song Cc: Liam R. Howlett Cc: Vlastimil Babka Cc: Mike Rapoport Cc: Suren Baghdasaryan Cc: Michal Hocko Cc: Ying Huang Cc: Ryan Roberts Cc: Chuanhua Han Cc: Signed-off-by: Sasha Levin --- mm/memory.c | 50 ++++++++++++++++++++++++++++++++++++-------------- 1 file changed, 36 insertions(+), 14 deletions(-) diff --git a/mm/memory.c b/mm/memory.c index d7f74ee122328..37b039cc7ba39 100644 --- a/mm/memory.c +++ b/mm/memory.c @@ -4198,6 +4198,34 @@ static struct folio *alloc_swap_folio(struct vm_fault *vmf) static DECLARE_WAIT_QUEUE_HEAD(swapcache_wq); +/* + * Get the address range in which a folio might be mapped, assuming its pages + * are mapped consecutively and the folio page at the given idx is mapped at + * the given address. + */ +static void folio_pte_range(const struct folio *folio, + const struct vm_area_struct *vma, unsigned long addr, + unsigned long idx, unsigned long *start, unsigned long *end) +{ + /* Stay within the page table and VMA boundaries. */ + const unsigned long pmd_start = addr & PMD_MASK; + const unsigned long pmd_end = pmd_start + PMD_SIZE; + const unsigned long lower = max(pmd_start, vma->vm_start); + /* + * We cannot use pmd_addr_end(), as it does not clamp reliably. To + * avoid wraparounds, compute using the inclusive end. + */ + const unsigned long upper = min(pmd_end - 1, vma->vm_end - 1) + 1; + const unsigned long offset = idx << PAGE_SHIFT; + + /* + * Avoid start/end addresses wrapping by not adding/subtracting more + * than the lower/upper limits would allow. + */ + *start = addr - min(addr - lower, offset); + *end = addr + min(upper - addr, folio_size(folio) - offset); +} + /* * We enter with either the VMA lock or the mmap_lock held (see * FAULT_FLAG_VMA_LOCK), and pte mapped but not yet locked. @@ -4445,16 +4473,15 @@ vm_fault_t do_swap_page(struct vm_fault *vmf) address = vmf->address; ptep = vmf->pte; if (folio_test_large(folio) && folio_test_swapcache(folio)) { - int nr = folio_nr_pages(folio); - unsigned long idx = folio_page_idx(folio, page); - unsigned long folio_start = address - idx * PAGE_SIZE; - unsigned long folio_end = folio_start + nr * PAGE_SIZE; + const int nr = folio_nr_pages(folio); + const unsigned long idx = folio_page_idx(folio, page); + unsigned long folio_start, folio_end; pte_t *folio_ptep; pte_t folio_pte; - if (unlikely(folio_start < max(address & PMD_MASK, vma->vm_start))) - goto check_folio; - if (unlikely(folio_end > pmd_addr_end(address, vma->vm_end))) + folio_pte_range(folio, vma, address, idx, &folio_start, + &folio_end); + if (unlikely((folio_end - folio_start) >> PAGE_SHIFT != nr)) goto check_folio; folio_ptep = vmf->pte - idx; @@ -5542,16 +5569,11 @@ static void numa_rebuild_large_mapping(struct vm_fault *vmf, struct vm_area_stru struct folio *folio, pte_t fault_pte, bool ignore_writable, bool pte_write_upgrade) { - int nr = pte_pfn(fault_pte) - folio_pfn(folio); + const unsigned long idx = pte_pfn(fault_pte) - folio_pfn(folio); unsigned long start, end, addr = vmf->address; - unsigned long addr_start = addr - (nr << PAGE_SHIFT); - unsigned long pt_start = ALIGN_DOWN(addr, PMD_SIZE); pte_t *start_ptep; - /* Stay within the VMA and within the page table. */ - start = max3(addr_start, pt_start, vma->vm_start); - end = min3(addr_start + folio_size(folio), pt_start + PMD_SIZE, - vma->vm_end); + folio_pte_range(folio, vma, addr, idx, &start, &end); start_ptep = vmf->pte - ((addr - start) >> PAGE_SHIFT); /* Restore all PTEs' mapping of the large folio */ -- 2.53.0