diff options
| author | Sebastian Andrzej Siewior <bigeasy@linutronix.de> | 2026-09-18 12:50:13 +0200 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2026-09-29 23:13:31 -0700 |
| commit | bfe990ef011ac0089fd4528089fcf1e839c28af8 (patch) | |
| tree | 8604ab4c7fca214d43b791922e1fde834c0a48bf /scripts | |
| parent | d450b11940e83bd3af5568e290df8fb58d6bbc15 (diff) | |
| download | linux-next-bfe990ef011ac0089fd4528089fcf1e839c28af8.tar.gz linux-next-bfe990ef011ac0089fd4528089fcf1e839c28af8.zip | |
mm/vmalloc: use %p for pointer formatting
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 controlled 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.
/proc/vmallocinfo has mode 0400, so this change doesn't make kernel
pointer information available to unprivileged userspace.
Link: https://lore.kernel.org/20260918105013.UpdykT6j@linutronix.de
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: SJ Park <sj@kernel.org>
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
