summaryrefslogtreecommitdiff
path: root/scripts/livepatch/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorThomas Weißschuh <thomas.weissschuh@linutronix.de>2025-04-07 10:25:09 +0200
committerLeon Romanovsky <leon@kernel.org>2025-04-09 14:30:10 -0400
commit9334003d1335b1d086334f946eab158503487e58 (patch)
tree4a2daf11a07d22b954c4f2ea61aaff4dfb60dc86 /scripts/livepatch/git@git.tavy.me:linux.git
parentb84001ad0ceeb34bc3fd6c383f197326d4fe8353 (diff)
RDMA: 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. Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de> Link: https://patch.msgid.link/20250407-restricted-pointers-infiniband-v1-1-22b20504b84d@linutronix.de Signed-off-by: Leon Romanovsky <leon@kernel.org>
Diffstat (limited to 'scripts/livepatch/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions