Re: [PATCH v3 2/2] mm/vmalloc: fix vmalloc_dump_obj cross-zone VA lookup
From: Uladzislau Rezki
Date: Fri Sep 25 2026 - 06:37:10 EST
On Thu, Sep 24, 2026 at 04:51:40PM +0800, Ye Liu wrote:
> From: Ye Liu <liuye@xxxxxxxxxx>
>
> 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@xxxxxxxxxx>
> ---
> 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;
>
Just set it to NULL once on entry?
> 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;
> + }
>
Can we simplify like?
...
va = find_vmap_area_lock(addr, &vn, VMAP_LOCK);
if (va)
spin_unlock(&vn->busy.lock);
return va;
...
Thanks!
--
Uladzislau Rezki