From: Ye Liu <ye.liu@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, Ye Liu <liuye@kylinos.cn>
Subject: [PATCH v3 2/2] mm/vmalloc: fix vmalloc_dump_obj cross-zone VA lookup
Date: Thu, 24 Sep 2026 16:51:40 +0800 [thread overview]
Message-ID: <20260924-vmalloc_dump_obj-v3-2-5bdee3da37b3@linux.dev> (raw)
In-Reply-To: <20260924-vmalloc_dump_obj-v3-0-5bdee3da37b3@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.
Extract find_vmap_area_lock() from find_vmap_area() to share the
cross-node iteration logic. The helper supports both spin_lock and
spin_trylock, the latter for atomic dump contexts (OOM, KASAN, RCU).
Signed-off-by: Ye Liu <liuye@kylinos.cn>
---
mm/vmalloc.c | 111 +++++++++++++++++++++++++++++++++++++----------------------
1 file changed, 69 insertions(+), 42 deletions(-)
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index df42d8a6f058..e5b465de1559 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -2517,39 +2517,81 @@ static void free_unmap_vmap_area(struct vmap_area *va)
free_vmap_area_noflush(va);
}
-struct vmap_area *find_vmap_area(unsigned long addr)
+static inline int next_vmap_node_id(int i)
+{
+ return (i + nr_vmap_nodes - 1) % nr_vmap_nodes;
+}
+
+enum vmap_lock_mode {
+ VMAP_LOCK,
+ VMAP_TRYLOCK,
+};
+
+/*
+ * Search for a vmap_area at @addr across all vmap nodes. An
+ * addr_to_node_id(addr) converts an address to a node index where
+ * a VA is located. If VA spans several zones and passed addr is not
+ * the same as va->va_start, what is not common, we may need to scan
+ * extra nodes. See an example:
+ *
+ * <----va---->
+ * -|-----|-----|-----|-----|-
+ * 1 2 0 1
+ *
+ * VA resides in node 1 whereas it spans 1, 2 an 0. If passed addr
+ * is within 2 or 0 nodes we should do extra work.
+ *
+ * Returns the VA with @locked_vn->busy.lock held; the caller must
+ * release it. If @mode is VMAP_TRYLOCK, nodes that cannot be locked
+ * are skipped.
+ */
+static struct vmap_area *
+find_vmap_area_lock(unsigned long addr, struct vmap_node **locked_vn,
+ enum vmap_lock_mode mode)
{
struct vmap_node *vn;
struct vmap_area *va;
int i, j;
- if (unlikely(!vmap_initialized))
+ if (unlikely(!vmap_initialized)) {
+ *locked_vn = NULL;
return NULL;
+ }
- /*
- * An addr_to_node_id(addr) converts an address to a node index
- * where a VA is located. If VA spans several zones and passed
- * addr is not the same as va->va_start, what is not common, we
- * may need to scan extra nodes. See an example:
- *
- * <----va---->
- * -|-----|-----|-----|-----|-
- * 1 2 0 1
- *
- * VA resides in node 1 whereas it spans 1, 2 an 0. If passed
- * addr is within 2 or 0 nodes we should do extra work.
- */
i = j = addr_to_node_id(addr);
do {
vn = &vmap_nodes[i];
- spin_lock(&vn->busy.lock);
+ if (mode == VMAP_LOCK) {
+ spin_lock(&vn->busy.lock);
+ } else {
+ if (!spin_trylock(&vn->busy.lock))
+ continue;
+ }
+
va = __find_vmap_area(addr, &vn->busy.root);
+ if (va) {
+ *locked_vn = vn;
+ return va;
+ }
+
spin_unlock(&vn->busy.lock);
+ } while ((i = next_vmap_node_id(i)) != j);
- if (va)
- return va;
- } while ((i = (i + nr_vmap_nodes - 1) % nr_vmap_nodes) != j);
+ *locked_vn = NULL;
+ return NULL;
+}
+
+struct vmap_area *find_vmap_area(unsigned long addr)
+{
+ struct vmap_node *vn;
+ struct vmap_area *va;
+
+ va = find_vmap_area_lock(addr, &vn, VMAP_LOCK);
+ if (va) {
+ spin_unlock(&vn->busy.lock);
+ return va;
+ }
return NULL;
}
@@ -2558,26 +2600,14 @@ static struct vmap_area *find_unlink_vmap_area(unsigned long addr)
{
struct vmap_node *vn;
struct vmap_area *va;
- int i, j;
-
- /*
- * Check the comment in the find_vmap_area() about the loop.
- */
- i = j = addr_to_node_id(addr);
- do {
- vn = &vmap_nodes[i];
- spin_lock(&vn->busy.lock);
- va = __find_vmap_area(addr, &vn->busy.root);
- if (va)
- unlink_va(va, &vn->busy.root);
+ va = find_vmap_area_lock(addr, &vn, VMAP_LOCK);
+ if (va) {
+ unlink_va(va, &vn->busy.root);
spin_unlock(&vn->busy.lock);
+ }
- if (va)
- return va;
- } while ((i = (i + nr_vmap_nodes - 1) % nr_vmap_nodes) != j);
-
- return NULL;
+ return va;
}
/*** Per cpu kva allocator ***/
@@ -5278,14 +5308,11 @@ 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;
- va = __find_vmap_area(addr, &vn->busy.root);
+ va = find_vmap_area_lock(addr, &vn, VMAP_TRYLOCK);
if (!va || !va->vm) {
- spin_unlock(&vn->busy.lock);
+ if (va)
+ spin_unlock(&vn->busy.lock);
return false;
}
--
2.25.1
prev parent reply other threads:[~2026-09-24 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 8:51 [PATCH v3 0/2] mm/vmalloc: fix vmalloc_dump_obj " Ye Liu
2026-09-24 8:51 ` [PATCH v3 1/2] mm/vmalloc: fix vmalloc_dump_obj address alignment for last-page lookups Ye Liu
2026-09-24 8:51 ` Ye Liu [this message]
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=20260924-vmalloc_dump_obj-v3-2-5bdee3da37b3@linux.dev \
--to=ye.liu@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liuye@kylinos.cn \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--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®