diff options
| author |   Thomas Weißschuh <thomas.weissschuh@linutronix.de> | 2025-02-17 14:13:56 +0100 |
|---|---|---|
| committer |   Janosch Frank <frankja@linux.ibm.com> | 2025-03-17 08:55:46 +0000 |
| commit | 6c9567e0850be2f0f94ab64fa6512413fd1a1eb1 (patch) | |
| tree | aba6b66ee20946cf5a9628360e29630c3fbc3525 | |
| parent | Linux 6.14-rc2 (diff) | |
| download | wireguard-linux-6c9567e0850be2f0f94ab64fa6512413fd1a1eb1.tar.xz wireguard-linux-6c9567e0850be2f0f94ab64fa6512413fd1a1eb1.zip | |
KVM: s390: Don't use %pK through tracepoints
Restricted pointers ("%pK") are not meant to be used through TP_format().
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>
Link: https://lore.kernel.org/r/20250217-restricted-pointers-s390-v1-1-0e4ace75d8aa@linutronix.de
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Message-ID: <20250217-restricted-pointers-s390-v1-1-0e4ace75d8aa@linutronix.de>
| -rw-r--r-- | arch/s390/kvm/trace-s390.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/arch/s390/kvm/trace-s390.h b/arch/s390/kvm/trace-s390.h index 9ac92dbf680d..9e28f165c114 100644 --- a/arch/s390/kvm/trace-s390.h +++ b/arch/s390/kvm/trace-s390.h @@ -56,7 +56,7 @@ TRACE_EVENT(kvm_s390_create_vcpu, __entry->sie_block = sie_block; ), - TP_printk("create cpu %d at 0x%pK, sie block at 0x%pK", + TP_printk("create cpu %d at 0x%p, sie block at 0x%p", __entry->id, __entry->vcpu, __entry->sie_block) ); @@ -255,7 +255,7 @@ TRACE_EVENT(kvm_s390_enable_css, __entry->kvm = kvm; ), - TP_printk("enabling channel I/O support (kvm @ %pK)\n", + TP_printk("enabling channel I/O support (kvm @ %p)\n", __entry->kvm) ); |