aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorThomas Weißschuh <[email protected]>2025-06-18 07:43:34 +0000
committerVinod Koul <[email protected]>2025-06-26 22:27:55 +0000
commit6e6d3c6f0ef235a95c25385b2dad98e8ad6223eb (patch)
tree6ae326d11425e9ac4b89927901a9e1ac58fee91e /tools/perf/scripts/python/export-to-postgresql.py
parentdmaengine: stm32-dma: configure next sg only if there are more than 2 sgs (diff)
downloadkernel-6e6d3c6f0ef235a95c25385b2dad98e8ad6223eb.tar.gz
kernel-6e6d3c6f0ef235a95c25385b2dad98e8ad6223eb.zip
dmaengine: stm32: 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 <[email protected]> Reviewed-by: Amelie Delaunay <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Vinod Koul <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions