From: Hao Ge <hao.ge@linux.dev>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: Suren Baghdasaryan <surenb@google.com>,
=Kent Overstreet <kent.overstreet@linux.dev>,
Luis Chamberlain <mcgrof@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Daniel Gomez <da.gomez@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Aaron Tomlin <atomlin@atomlin.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
Michal Hocko <mhocko@suse.com>,
Brendan Jackman <brendan.jackman@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-modules@vger.kernel.org, kasan-dev@googlegroups.com,
Sashiko <sashiko-bot@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v11 2/7] mm/vmalloc: undo partial mappings inside the mapping functions
Date: Thu, 8 Oct 2026 16:13:18 +0800 [thread overview]
Message-ID: <896c2dc7-4787-4c22-90dc-a3cd607be6fa@linux.dev> (raw)
In-Reply-To: <a15de109-a88a-49f8-80cc-7bf216d6954d@linux.dev>
On 2026/10/8 14:53, Hao Ge wrote:
> Hi Uladzislau
>
>
> On 2026/9/30 18:12, Uladzislau Rezki wrote:
>> On Tue, Sep 29, 2026 at 04:20:09PM +0800, Hao Ge wrote:
>>> __vmap_pages_range_noflush() and friends can install some PTEs before
>>> failing and leave them mapped, and the kernel callers do not agree on
>>> who cleans them up. For example, pcpu_map_pages() and
>>> kmsan_ioremap_page_range() unmap the leftovers themselves, while
>>> vm_module_tags_populate() and the __GFP_NOFAIL retry loop in
>>> __vmalloc_area_node() relied on the mapping functions cleaning up and
>>> did not call anything like vunmap_range() themselves. When the same
>>> range is mapped again, the attempt hits the leftovers and fails, with
>>> BUG() in vmap_pte_range() for huge mappings.
>>>
>>> After discussing with Suren and Ulad, we decided the cleanup belongs
>>> to __vmap_pages_range_noflush() and friends, so the callers no longer
>>> need to unmap the partial mappings themselves. Each function now
>>> undoes the PTEs it installed itself.
>>>
>>> The rollback calls the low-level __vunmap_range_noflush(), it just
>>> clears the PTEs of the range it is given, which is all a rollback
>>> needs. It cannot use vunmap_range_noflush() because these mapping
>>> functions also map the KMSAN shadow and origin, and for a metadata
>>> range its hook would look up the metadata of the metadata, get 0
>>> and BUG() on addr >= end. The failed mappings were never accessed,
>>> no TLB flush needed.
>>>
>>> Fixes: 9376130c390a ("mm/vmalloc: add support for __GFP_NOFAIL")
>>> Fixes: 0f9b685626da ("alloc_tag: populate memory for module tags as needed")
>>> Reported-by: Sashiko <sashiko-bot@kernel.org>
>>> Cc: stable@vger.kernel.org
>>> Signed-off-by: Hao Ge <hao.ge@linux.dev>
>>> ---
>>> mm/kmsan/shadow.c | 4 ++++
>>> mm/vmalloc.c | 31 +++++++++++++++++++++++++++++--
>>> 2 files changed, 33 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/mm/kmsan/shadow.c b/mm/kmsan/shadow.c
>>> index 0c88d89bf0d6..2166086d3dc3 100644
>>> --- a/mm/kmsan/shadow.c
>>> +++ b/mm/kmsan/shadow.c
>>> @@ -258,6 +258,10 @@ int kmsan_vmap_pages_range_noflush(unsigned long start, unsigned long end,
>>> o_pages, page_shift);
>>> kmsan_leave_runtime();
>>> if (mapped) {
>>> + /* Undo the shadow mapping set up above. */
>>> + kmsan_enter_runtime();
>>> + __vunmap_range_noflush(shadow_start, shadow_end);
>>> + kmsan_leave_runtime();
>>> err = mapped;
>>> goto ret;
>>> }
>>>
>> Can we just do that inside the vmalloc? For example in the
>> __vmap_pages_range_noflush() as entry function for all(?) helpers?
>> So we do not need do it manually?
>>
> The hunk was for the failure path in kmsan_vmap_pages_range_noflush().
> Shadow and origin are mapped there as two separate calls, and when
> the origin one fails the shadow is already up. __vmap_pages_range_noflush()
> cannot do that undo, it only sees its own range.
>
> kmsan_vmap_pages_range_noflush() has a single caller, so if we were to move this
> logic into vmalloc, it would require some modifications as follows:
>
> @@ -712,9 +724,14 @@ int vmap_pages_range_noflush(unsigned long addr, unsigned long end,
> int ret = kmsan_vmap_pages_range_noflush(addr, end, prot, pages,
> page_shift, gfp_mask);
>
> + if (!ret)
> + ret = __vmap_pages_range_noflush(addr, end, prot, pages,
> + page_shift);
> + /* Undo whatever was mapped before the failure. */
> if (ret)
> - return ret;
> - return __vmap_pages_range_noflush(addr, end, prot, pages, page_shift);
> + kmsan_vunmap_range_noflush(addr, end);
> +
> + return ret;
> }
>
I'd rather put this logic inside kmsan_vmap_pages_range_noflush.
This function should clean things up on its own, not depend on
the caller to do it, just like kmsan_ioremap_page_range.
https://elixir.bootlin.com/linux/v7.3-rc5/source/mm/kmsan/hooks.c#L185
Uladzislau, WDYT?
Thanks
Best Regards
Hao
>>> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
>>> index 859e6d2d57a3..9bbf75706627 100644
>>> --- a/mm/vmalloc.c
>>> +++ b/mm/vmalloc.c
>>> @@ -349,6 +349,10 @@ static int vmap_range_noflush(unsigned long addr, unsigned long end,
>>> if (mask & ARCH_PAGE_TABLE_SYNC_MASK)
>>> arch_sync_kernel_mappings(start, end);
>>>
>>> + /* Undo the PTEs installed before the failure. */
>>> + if (err)
>>> + __vunmap_range_noflush(start, end);
>>> +
>>> return err;
>>> }
>>>
>>> @@ -363,6 +367,9 @@ int vmap_page_range(unsigned long addr, unsigned long end,
>>> if (!err)
>>> err = kmsan_ioremap_page_range(addr, end, phys_addr, prot,
>>> ioremap_max_page_shift);
>>> + if (err)
>>> + __vunmap_range_noflush(addr, end);
>>> +
>>> return err;
>>> }
>>>
>>> @@ -667,6 +674,10 @@ static int vmap_small_pages_range_noflush(unsigned long addr, unsigned long end,
>>> if (mask & ARCH_PAGE_TABLE_SYNC_MASK)
>>> arch_sync_kernel_mappings(start, end);
>>>
>>> + /* Undo the PTEs installed before the failure. */
>>> + if (err)
>>> + __vunmap_range_noflush(start, end);
>>> +
>>> return err;
>>> }
>>>
>> The only one user of that function is __vmap_pages_range_noflush()
>> so we can cover both cases there small and huge path.
>>
>> Is that enough just to do unroll in the below:
>>
>> __vmap_pages_range_noflush()
>> vmap_page_range()
>>
>> functions? It will also fix NOFAIL case:
>>
>
> I see. right, __vmap_pages_range_noflush() is just above the
> actual page‑table mapping, so it's low‑level enough.
> Thanks a lot for your prototype.
>
> I'm tidying up the code and will post a REF patch afterwards.
>
> Thanks
> Best Regards
> Hao
>
>> <snip>
>> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
>> index 89c327a6ce7d..fa1f357ecf3f 100644
>> --- a/mm/vmalloc.c
>> +++ b/mm/vmalloc.c
>> @@ -359,10 +359,19 @@ int vmap_page_range(unsigned long addr, unsigned long end,
>>
>> err = vmap_range_noflush(addr, end, phys_addr, pgprot_nx(prot),
>> ioremap_max_page_shift);
>> + if (err)
>> + goto error_cleanup_range;
>> +
>> flush_cache_vmap(addr, end);
>> - if (!err)
>> - err = kmsan_ioremap_page_range(addr, end, phys_addr, prot,
>> + err = kmsan_ioremap_page_range(addr, end, phys_addr, prot,
>> ioremap_max_page_shift);
>> + if (err)
>> + goto error_cleanup_range;
>> +
>> + return 0;
>> +
>> +error_cleanup_range:
>> + __vunmap_range_noflush(addr, end);
>> return err;
>> }
>>
>> @@ -683,26 +692,35 @@ int __vmap_pages_range_noflush(unsigned long addr, unsigned long end,
>> pgprot_t prot, struct page **pages, unsigned int page_shift)
>> {
>> unsigned int i, nr = (end - addr) >> PAGE_SHIFT;
>> + unsigned long start = addr;
>> + int err;
>>
>> - WARN_ON(page_shift < PAGE_SHIFT);
>> -
>> - if (!IS_ENABLED(CONFIG_HAVE_ARCH_HUGE_VMALLOC) ||
>> - page_shift == PAGE_SHIFT)
>> - return vmap_small_pages_range_noflush(addr, end, prot, pages);
>> + if (WARN_ON(addr >= end))
>> + return -EINVAL;
>>
>> - for (i = 0; i < nr; i += 1U << (page_shift - PAGE_SHIFT)) {
>> - int err;
>> + if (WARN_ON(page_shift < PAGE_SHIFT))
>> + return -EINVAL;
>>
>> - err = vmap_range_noflush(addr, addr + (1UL << page_shift),
>> + if (!IS_ENABLED(CONFIG_HAVE_ARCH_HUGE_VMALLOC) ||
>> + page_shift == PAGE_SHIFT) {
>> + err = vmap_small_pages_range_noflush(addr, end, prot, pages);
>> + } else {
>> + for (i = 0; i < nr; i += 1U << (page_shift - PAGE_SHIFT)) {
>> + err = vmap_range_noflush(addr, addr + (1UL << page_shift),
>> page_to_phys(pages[i]), prot,
>> page_shift);
>> - if (err)
>> - return err;
>> + if (err)
>> + break;
>>
>> - addr += 1UL << page_shift;
>> + addr += 1UL << page_shift;
>> + }
>> }
>>
>> - return 0;
>> + if (err)
>> + __vunmap_range_noflush(start, end);
>> +
>> + /* 0 on success. */
>> + return err;
>> }
>>
>> int vmap_pages_range_noflush(unsigned long addr, unsigned long end,
>> @@ -714,7 +732,13 @@ int vmap_pages_range_noflush(unsigned long addr, unsigned long end,
>>
>> if (ret)
>> return ret;
>> - return __vmap_pages_range_noflush(addr, end, prot, pages, page_shift);
>> +
>> + ret = __vmap_pages_range_noflush(addr, end, prot, pages, page_shift);
>> + if (ret)
>> + /* Cleanup KMSAN metadata. */
>> + kmsan_vunmap_range_noflush(addr, end);
>> +
>> + return ret;
>> }
>>
>> static int __vmap_pages_range(unsigned long addr, unsigned long end,
>> <snip>
>>
>> --
>> Uladzislau Rezki
next prev parent reply other threads:[~2026-10-08 8:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 8:20 [PATCH v11 0/7] alloc_tag and module codetag section fixes Hao Ge
2026-09-29 8:20 ` [PATCH v11 1/7] alloc_tag: move release_module_tags() above reserve_module_tags() Hao Ge
2026-09-29 8:20 ` [PATCH v11 2/7] mm/vmalloc: undo partial mappings inside the mapping functions Hao Ge
2026-09-30 10:12 ` Uladzislau Rezki
2026-10-04 17:42 ` Suren Baghdasaryan
2026-10-08 6:53 ` Hao Ge
2026-10-08 8:09 ` Hao Ge
2026-10-08 8:13 ` Hao Ge [this message]
2026-09-29 8:20 ` [PATCH v11 3/7] alloc_tag: clean up the populate failure path Hao Ge
2026-10-04 17:55 ` Suren Baghdasaryan
2026-09-29 8:20 ` [PATCH v11 4/7] module: introduce SH_ENTSIZE_STANDALONE for separately allocated sections Hao Ge
2026-09-29 8:20 ` [PATCH v11 5/7] module: allocate codetag sections before the regular module layout Hao Ge
2026-09-29 8:20 ` [PATCH v11 6/7] alloc_tag: skip percpu counter allocation when profiling is disabled Hao Ge
2026-09-29 8:20 ` [PATCH v11 7/7] alloc_tag: fix the /proc/allocinfo lifecycle Hao Ge
2026-10-04 18:23 ` Suren Baghdasaryan
2026-09-29 20:44 ` [PATCH v11 0/7] alloc_tag and module codetag section fixes Andrew Morton
2026-09-30 2:39 ` Suren Baghdasaryan
2026-09-30 3:26 ` Hao Ge
2026-09-30 8:34 ` Uladzislau Rezki
2026-10-04 17:42 ` Suren Baghdasaryan
2026-10-04 18:37 ` Suren Baghdasaryan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=896c2dc7-4787-4c22-90dc-a3cd607be6fa@linux.dev \
--to=hao.ge@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=atomlin@atomlin.com \
--cc=brendan.jackman@linux.dev \
--cc=da.gomez@kernel.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=hannes@cmpxchg.org \
--cc=kasan-dev@googlegroups.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mhocko@suse.com \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=urezki@gmail.com \
--cc=vbabka@kernel.org \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®