diff options
| author | Thomas Weißschuh <thomas.weissschuh@linutronix.de> | 2025-02-17 16:13:57 +0300 |
|---|---|---|
| committer | Janosch Frank <frankja@linux.ibm.com> | 2025-03-17 11:55:46 +0300 |
| commit | 0c7fbae5bc782429c97d68dc40fb126748d7e352 (patch) | |
| tree | 42e6d647343247f3491d82758efe002924c94597 /tools/perf/scripts/python/check-perf-trace.py | |
| parent | 6c9567e0850be2f0f94ab64fa6512413fd1a1eb1 (diff) | |
| download | linux-0c7fbae5bc782429c97d68dc40fb126748d7e352.tar.xz | |
KVM: s390: Don't use %pK through debug printing
Restricted pointers ("%pK") are only meant to be used when directly
printing to a file from task context.
Otherwise it can unintentionally expose security sensitive,
raw pointer values.
Use regular pointer formatting instead.
Link: https://lore.kernel.org/lkml/20250113171731-dc10e3c1-da64-4af0-b767-7c7070468023@linutronix.de/
Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Reviewed-by: Michael Mueller <mimu@linux.ibm.com>
Tested-by: Michael Mueller <mimu@linux.ibm.com>
Link: https://lore.kernel.org/r/20250217-restricted-pointers-s390-v1-2-0e4ace75d8aa@linutronix.de
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Message-ID: <20250217-restricted-pointers-s390-v1-2-0e4ace75d8aa@linutronix.de>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions