From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>
Subject: [PATCH] mm/vmalloc: Use %p for pointer formatting
Date: Fri, 18 Sep 2026 12:50:13 +0200 [thread overview]
Message-ID: <20260918105013.UpdykT6j@linutronix.de> (raw)
Commit 45ec16908e84e ("mm: use %pK for /proc/vmallocinfo") introduced
the %pK in order not to leak kernel pointers.
Since commit ad67b74d2469d ("printk: hash addresses printed with
%p") pointers are hashed by default and the behaviour can be controller
by `hash_pointers' boot argument.
The policy on %p is to not introduce new ones.
Removing %pK makes it possible to remove its handling from the library.
Looking at the output, having the pointer in the output makes it
possible to distinguish the individual entries.
Use %p instead %pK.
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
mm/vmalloc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index bea9f76ed7e74..6461336f899bc 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -5308,7 +5308,7 @@ static void show_purge_info(struct seq_file *m)
for_each_vmap_node(vn) {
spin_lock(&vn->lazy.lock);
list_for_each_entry(va, &vn->lazy.head, list) {
- seq_printf(m, "0x%pK-0x%pK %7ld unpurged vm_area\n",
+ seq_printf(m, "0x%p-0x%p %7ld unpurged vm_area\n",
(void *)va->va_start, (void *)va->va_end,
va_size(va));
}
@@ -5331,7 +5331,7 @@ static int vmalloc_info_show(struct seq_file *m, void *p)
list_for_each_entry(va, &vn->busy.head, list) {
if (!va->vm) {
if (va->flags & VMAP_RAM)
- seq_printf(m, "0x%pK-0x%pK %7ld vm_map_ram\n",
+ seq_printf(m, "0x%p-0x%p %7ld vm_map_ram\n",
(void *)va->va_start, (void *)va->va_end,
va_size(va));
@@ -5345,7 +5345,7 @@ static int vmalloc_info_show(struct seq_file *m, void *p)
/* Pair with smp_wmb() in clear_vm_uninitialized_flag() */
smp_rmb();
- seq_printf(m, "0x%pK-0x%pK %7ld",
+ seq_printf(m, "0x%p-0x%p %7ld",
v->addr, v->addr + v->size, v->size);
if (v->caller)
--
2.55.0
next reply other threads:[~2026-09-18 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 10:50 Sebastian Andrzej Siewior [this message]
2026-09-18 20:05 ` [PATCH] mm/vmalloc: Use %p for pointer formatting Andrew Morton
2026-09-18 20:14 ` Sebastian Andrzej Siewior
2026-09-19 0:39 ` SJ Park
2026-09-19 7:23 ` Uladzislau Rezki
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=20260918105013.UpdykT6j@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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