From: Uladzislau Rezki <urezki@gmail.com>
To: Ye Liu <ye.liu@linux.dev>
Cc: 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>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, Ye Liu <liuye@kylinos.cn>
Subject: Re: [PATCH v2 2/3] mm/vmalloc: fix vmalloc_dump_obj cross-zone VA lookup
Date: Tue, 22 Sep 2026 14:44:44 +0200 [thread overview]
Message-ID: <arJ4PLGlF7uhNWOs@milan> (raw)
In-Reply-To: <20260921-vmalloc_dump_obj-v2-2-73fceb3ed1c8@linux.dev>
On Mon, Sep 21, 2026 at 09:17:22PM +0800, Ye Liu wrote:
> 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
>
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 89c327a6ce7d..3719dc02dcaf 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -2511,7 +2511,22 @@ 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,
+};
+
+/*
+ * Add a comment here.
+ */
+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;
@@ -2534,16 +2549,40 @@ struct vmap_area *find_vmap_area(unsigned long addr)
* 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;
}
and we use the helper in the vmalloc_dump_obj()?
--
Uladzislau Rezki
next prev parent reply other threads:[~2026-09-22 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 13:17 [PATCH v2 0/3] mm/vmalloc: fix vmalloc_dump_obj " Ye Liu
2026-09-21 13:17 ` [PATCH v2 1/3] mm/vmalloc: fix vmalloc_dump_obj address alignment for last-page lookups Ye Liu
2026-09-22 12:17 ` Uladzislau Rezki
2026-09-21 13:17 ` [PATCH v2 2/3] mm/vmalloc: fix vmalloc_dump_obj cross-zone VA lookup Ye Liu
2026-09-22 12:44 ` Uladzislau Rezki [this message]
2026-09-23 3:39 ` Ye Liu
2026-09-21 13:17 ` [PATCH v2 3/3] mm/vmalloc: skip vmalloc_dump_obj for non-vmalloc addresses Ye Liu
2026-09-22 12:13 ` Uladzislau Rezki
2026-09-23 3:48 ` Ye Liu
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=arJ4PLGlF7uhNWOs@milan \
--to=urezki@gmail.com \
--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=ye.liu@linux.dev \
/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®