[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aIcuWxhtNrULHvnO@alpha.franken.de>
Date: Mon, 28 Jul 2025 10:01:31 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: Huacai Chen <chenhuacai@...nel.org>, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [PATCH RESEND] MIPS: Don't use %pK through printk
On Fri, Jul 18, 2025 at 03:18:24PM +0200, Thomas Weißschuh wrote:
> Restricted pointers ("%pK") are not meant to be used through printk().
> It can unintentionally expose security sensitive, raw pointer values.
>
> Use regular pointer formatting instead.
>
> Link: https://lore.kernel.org/lkml/20250113171731-dc10e3c1-da64-4af0-b767-7c7070468023@linutronix.de/
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
> ---
> arch/mips/kernel/relocate.c | 10 +++++-----
> arch/mips/kvm/mips.c | 2 +-
> arch/mips/mm/physaddr.c | 2 +-
> 3 files changed, 7 insertions(+), 7 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists