Thread (7 messages) flat view 7 messages, 4 authors, 24d ago

Re: [PATCH net-next v3] net: Replace %pK output with 0

From: Jakub Kicinski <kuba@kernel.org>
Date: 2026-08-14 13:55:43
Also in: linux-can, linux-sctp

On Fri, 14 Aug 2026 12:58:12 +0200 Sebastian Andrzej Siewior wrote:
quoted
We have upgraded the slop...itifier since v2, it has more comments now...
The one about %ps potentially leaking more rather than less looks legit?  
It complains about %ps leaking the pointer if kallsym is switched off.
This isn't unique to can and I pointed this out to Kees. 
Oliver Hartkopp mentioned that he wanted to rework the can output.

I'm going to tell vsprintf to route the %ps output the same as %p for
!kallsym so this goes away. 

Depending on what you prefer we can keep it as it or I drop the can bits
and repost everything else as-it. And then address later the other
sashiko bits where the documentation mentions "location of socket in
memory".
Not my expertise, TBH, I'd err on the side of caution since these are
security/hardening measures. IDK how much this all matters, or if
anyone uses !kallsym. 

Note that any rework has a solid chance of missing 7.3.

It should be most expedient to take the controversial part out and
repost. Or we can ask Kees for a recommendation?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help