aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorThomas Weißschuh <thomas.weissschuh@linutronix.de>2025-04-17 15:19:10 +0200
committerJeff Johnson <jeff.johnson@oss.qualcomm.com>2025-04-17 15:49:35 -0700
commit75f90ba47b2cda7de7a7bc1d099172516f6f96fa (patch)
treec5460bbab4d2a370f1c8567157681a893801d776 /tools/perf/scripts/python/export-to-postgresql.py
parentwifi: ath12k: Don't use %pK through printk (diff)
downloadwireguard-linux-75f90ba47b2cda7de7a7bc1d099172516f6f96fa.tar.xz
wireguard-linux-75f90ba47b2cda7de7a7bc1d099172516f6f96fa.zip
wifi: wcn36xx: Don't use %pK through printk
In the past %pK was preferable to %p as it would not leak raw pointer values into the kernel log. Since commit ad67b74d2469 ("printk: hash addresses printed with %p") the regular %p has been improved to avoid this issue. Furthermore, restricted pointers ("%pK") were never meant to be used through printk(). They can still unintentionally leak raw pointers or acquire sleeping looks in atomic contexts. Switch to the regular pointer formatting which is safer and easier to reason about. There are still a few users of %pK left, but these use it through seq_file, for which its usage is safe. Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de> Acked-by: Loic Poulain <loic.poulain@oss.qualcomm.com> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com> Link: https://patch.msgid.link/20250417-restricted-pointers-ath-v1-4-4e9a04dbe362@linutronix.de Signed-off-by: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions