crypto: ccree - Don't use %pK through printk
authorThomas Weißschuh <thomas.weissschuh@linutronix.de>
Wed, 18 Jun 2025 07:10:18 +0000 (09:10 +0200)
committerHerbert Xu <herbert@gondor.apana.org.au>
Mon, 23 Jun 2025 09:00:27 +0000 (17:00 +0800)
commitc71187c17f0b9fa7a567f09fc079369ae3970e85
treed416deed5fd96e0f6a53c60831ea4e67aef3407c
parente109b8ee1a3d5665f2f60612a60ad6c95339f5d3
crypto: ccree - 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>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
drivers/crypto/ccree/cc_buffer_mgr.c
drivers/crypto/ccree/cc_cipher.c
drivers/crypto/ccree/cc_hash.c