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 3/3] mm/vmalloc: skip vmalloc_dump_obj for non-vmalloc addresses
Date: Wed, 16 Sep 2026 16:25:30 +0800 [thread overview]
Message-ID: <20260916-vmalloc_dump_obj-v1-3-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() unconditionally searches all vmap nodes even when
called with a non-vmalloc address (e.g. a slab or stack pointer from
mem_dump_obj()). Add an is_vmalloc_addr() check at the entry to
avoid the unnecessary per-node trylock and rb-tree traversal.
The KASAN caller already gates on is_vmalloc_addr(), but mem_dump_obj()
calls vmalloc_dump_obj() before the fallback type check, so the guard
in the callee covers both paths without requiring caller changes.
Signed-off-by: Ye Liu <liuye@kylinos.cn>
---
mm/vmalloc.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 30c610f678dc..b3e706fde202 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -5277,6 +5277,9 @@ bool vmalloc_dump_obj(void *object)
unsigned long addr;
unsigned long nr_pages;
+ if (!is_vmalloc_addr(object))
+ return false;
+
addr = PAGE_ALIGN_DOWN((unsigned long) object);
/*
--
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 VA lookup 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 ` [PATCH 2/3] mm/vmalloc: fix vmalloc_dump_obj cross-zone VA lookup Ye Liu
2026-09-16 8:25 ` Ye Liu [this message]
2026-09-17 0:59 ` [PATCH 0/3] mm/vmalloc: fix vmalloc_dump_obj " 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-3-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®