From: Ye Liu <ye.liu@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Ye Liu <liuye@kylinos.cn>
Subject: [PATCH 2/3] mm/vmalloc: fix vmalloc_dump_obj cross-zone VA lookup
Date: Wed, 16 Sep 2026 16:25:29 +0800 [thread overview]
Message-ID: <20260916-vmalloc_dump_obj-v1-2-7aa402d224df@linux.dev> (raw)
In-Reply-To: <20260916-vmalloc_dump_obj-v1-0-7aa402d224df@linux.dev>
From: Ye Liu <liuye@kylinos.cn>
vmalloc_dump_obj() searches only one vmap node (addr_to_node(addr)),
but a vmalloc allocation may span multiple vmap zones. The VA is
stored in only one node's rb-tree (addr_to_node(va_start)), so an
object pointer in a different zone than va_start maps to a different
node and the search misses. This affects any allocation larger than
vmap_zone_size (64 KiB) on multi-CPU systems.
Iterate all vmap nodes using for_each_vmap_node, like find_vmap_area()
does, but with spin_trylock instead of spin_lock as this function can
be called from atomic dump contexts (OOM, KASAN, RCU).
Signed-off-by: Ye Liu <liuye@kylinos.cn>
---
mm/vmalloc.c | 24 ++++++++++++++++++------
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index df42d8a6f058..30c610f678dc 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -5278,17 +5278,29 @@ bool vmalloc_dump_obj(void *object)
unsigned long nr_pages;
addr = PAGE_ALIGN_DOWN((unsigned long) object);
- vn = addr_to_node(addr);
- if (!spin_trylock(&vn->busy.lock))
- return false;
+ /*
+ * A vmalloc allocation may span multiple vmap zones, so the
+ * node whose rb-tree holds the VA may differ from the node
+ * the address maps to. Search all nodes. Use trylock as
+ * this function can be called from atomic dump contexts.
+ */
+ va = NULL;
+ for_each_vmap_node(vn) {
+ if (!spin_trylock(&vn->busy.lock))
+ continue;
+
+ va = __find_vmap_area(addr, &vn->busy.root);
+ if (va && va->vm)
+ break;
- va = __find_vmap_area(addr, &vn->busy.root);
- if (!va || !va->vm) {
spin_unlock(&vn->busy.lock);
- return false;
+ va = NULL;
}
+ if (!va)
+ return false;
+
vm = va->vm;
addr = (unsigned long) vm->addr;
caller = vm->caller;
--
2.25.1
next prev parent reply other threads:[~2026-09-16 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 8:25 [PATCH 0/3] mm/vmalloc: fix vmalloc_dump_obj " Ye Liu
2026-09-16 8:25 ` [PATCH 1/3] mm/vmalloc: fix vmalloc_dump_obj address alignment for last-page lookups Ye Liu
2026-09-16 8:25 ` Ye Liu [this message]
2026-09-16 8:25 ` [PATCH 3/3] mm/vmalloc: skip vmalloc_dump_obj for non-vmalloc addresses Ye Liu
2026-09-17 0:59 ` [PATCH 0/3] mm/vmalloc: fix vmalloc_dump_obj VA lookup Andrew Morton
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=20260916-vmalloc_dump_obj-v1-2-7aa402d224df@linux.dev \
--to=ye.liu@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=urezki@gmail.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®