drivers: virt: acrn: Don't use %pK through printk
authorThomas Weißschuh <thomas.weissschuh@linutronix.de>
Fri, 18 Jul 2025 13:43:49 +0000 (15:43 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 24 Jul 2025 09:42:01 +0000 (11:42 +0200)
commit93b17c6afa83fda8eea4490aad9a3721eb6627bb
tree8688d72b51a6797d6eaebdd0150cd97aa9f08395
parenta6d283c526f96595e61a46c7901aecc92645f345
drivers: virt: acrn: 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>
Link: https://lore.kernel.org/r/20250718-restricted-pointers-virt-v1-1-12913fceaf52@linutronix.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/virt/acrn/ioreq.c
drivers/virt/acrn/mm.c