From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,urezki@gmail.com,liuye@kylinos.cn,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-vmalloc-group-xa_init-with-vbq-field-initializations.patch removed from -mm tree
Date: Mon, 12 Oct 2026 21:31:55 -0700 [thread overview]
Message-ID: <20261013043155.9A4A41F000FF@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/vmalloc: group xa_init with vbq field initializations
has been removed from the -mm tree. Its filename was
mm-vmalloc-group-xa_init-with-vbq-field-initializations.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Ye Liu <liuye@kylinos.cn>
Subject: mm/vmalloc: group xa_init with vbq field initializations
Date: Tue, 15 Sep 2026 10:43:30 +0800
Patch series "mm/vmalloc: minor cleanups", v2.
Small cleanup series for mm/vmalloc.c, no functional changes:
- Group xa_init() with the other vmap_block_queue field initializations
in vmalloc_init(), instead of after the unrelated vfree_deferred setup.
- Extract vmap_insert_free_area() helper to deduplicate the allocate-
and-insert pattern that appeared both inside the loop body and after
the loop in vmap_init_free_space().
- Extract show_busy_info() from vmalloc_info_show(), mirroring the
existing show_purge_info() pattern, so the top-level show function
only orchestrates the two data sources.
This patch (of 3):
Move xa_init() next to the other vbq field initializations instead of
after the unrelated vfree_deferred setup.
Link: https://lore.kernel.org/20260915-vmalloc_study-v2-0-cc4dfe635e22@linux.dev
Link: https://lore.kernel.org/20260915-vmalloc_study-v2-1-cc4dfe635e22@linux.dev
Signed-off-by: Ye Liu <liuye@kylinos.cn>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
---
mm/vmalloc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/mm/vmalloc.c~mm-vmalloc-group-xa_init-with-vbq-field-initializations
+++ a/mm/vmalloc.c
@@ -5561,10 +5561,11 @@ void __init vmalloc_init(void)
vbq = &per_cpu(vmap_block_queue, i);
spin_lock_init(&vbq->lock);
INIT_LIST_HEAD(&vbq->free);
+ xa_init(&vbq->vmap_blocks);
+
p = &per_cpu(vfree_deferred, i);
init_llist_head(&p->list);
INIT_WORK(&p->wq, delayed_vfree_work);
- xa_init(&vbq->vmap_blocks);
}
/*
_
Patches currently in -mm which might be from liuye@kylinos.cn are
mm-vmalloc-fix-vmalloc_dump_obj-address-alignment-for-last-page-lookups.patch
mm-vmalloc-fix-vmalloc_dump_obj-cross-zone-va-lookup.patch
reply other threads:[~2026-10-13 4:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261013043155.9A4A41F000FF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=liuye@kylinos.cn \
--cc=mm-commits@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.