diff options
| author | Sebastian Andrzej Siewior <bigeasy@linutronix.de> | 2026-09-18 12:48:52 +0200 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2026-09-18 14:05:53 -1000 |
| commit | a408c6d27f96e401d6da2b69c5b6f0c31a48a923 (patch) | |
| tree | dae4b3f28d92563f0ae6bf4edd3fbdb035fbbb05 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | e8f69fe59a104b4a97a3365dbb43c72996c2acde (diff) | |
| download | linux-next-a408c6d27f96e401d6da2b69c5b6f0c31a48a923.tar.gz linux-next-a408c6d27f96e401d6da2b69c5b6f0c31a48a923.zip | |
cgroup: Use %p for pointer formatting
Since ad67b74d2469 ("printk: hash addresses printed with %p") %p is hashed
by default, which is also what %pK prints under the default kptr_restrict=0.
Converting the remaining %pK users makes it possible to remove its handling
from vsprintf.
Documentation/process/deprecated.rst asks that no new %p uses be added, but
these pointers are what makes the css_set debug output useful, and debug.c
already prints css pointers with %p. Keep the pointer output and use %p.
Under kptr_restrict=1 and 2 the files now show the same hashed values as any
other %p output: unprivileged readers see hashes instead of zeros, and a
CAP_SYSLOG reader under kptr_restrict=1 no longer gets raw addresses.
Booting with hash_pointers=never is the remaining way to see them.
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Acked-by: Michal Koutný <mkoutny@suse.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
