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:21:54 +0200
committerJohannes Berg <johannes.berg@intel.com>2025-04-23 15:36:04 +0200
commitcfec9f8f58a9a7b8005a8a66f51b1f7752292301 (patch)
tree124f8c89e215c9fb6b30539f88986b3c0f0f75e7 /tools/perf/scripts/python/export-to-postgresql.py
parentwifi: brcmsmac: Spelling corrections (diff)
downloadwireguard-linux-cfec9f8f58a9a7b8005a8a66f51b1f7752292301.tar.xz
wireguard-linux-cfec9f8f58a9a7b8005a8a66f51b1f7752292301.zip
wifi: mwifiex: 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> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com> Acked-by: Brian Norris <briannorris@chromium.org> Link: https://patch.msgid.link/20250417-restricted-pointers-wifi-v1-1-b79cdaae5579@linutronix.de Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions