aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorThomas Weißschuh <thomas.weissschuh@linutronix.de>2025-08-11 09:44:42 +0200
committerRob Clark <robin.clark@oss.qualcomm.com>2025-08-18 07:50:49 -0700
commit1ba9fbe40337e448b32e2831a7051191d61f0382 (patch)
tree0d090216f878194da054baf35f5a81c5ac3f4031 /tools/perf/scripts/python
parentsoc: qcom: ubwc: Add missing UBWC config for SM7225 (diff)
downloadwireguard-linux-1ba9fbe40337e448b32e2831a7051191d61f0382.tar.xz
wireguard-linux-1ba9fbe40337e448b32e2831a7051191d61f0382.zip
drm/msm: 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 locks in atomic contexts. Switch to the regular pointer formatting which is safer and easier to reason about. Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Patchwork: https://patchwork.freedesktop.org/patch/667895/ Signed-off-by: Rob Clark <robin.clark@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions