From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Emil Tsalapatis <emil@etsalapatis.com>
Cc: bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH bpf-next] selftests/bpf: Replace %pK output with 0
Date: Tue, 15 Sep 2026 08:48:11 +0200 [thread overview]
Message-ID: <20260915064811.MrdbYUsX@linutronix.de> (raw)
In-Reply-To: <DLFFP4P6CAA6.QLQ38A75G2IZ@etsalapatis.com>
On 2026-09-14 23:39:22 [+0000], Emil Tsalapatis wrote:
> On Fri Sep 11, 2026 at 2:50 PM UTC, Sebastian Andrzej Siewior wrote:
> > Networking used to print the socket pointer with %p as output in the
> > /proc interface. This was later changed to %pK in order not to reveal
> > the actual pointer value. The output format has then been copied to bpf
> > tests which produce the same format including the %pK format modifier.
> >
> > Networking recently replaced the socket output with a plain 0 because
> > the socket pointer added no value to the output and the %pK should be
> > removed fom library handling. The format remained otherwise unchanged in
> > order not to break any tools which are parsing this information.
> >
> > This change removes the %pK modifier from bpf, following the change in
> > networking.
> >
> > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>
> Reviewed-by: Emil Tsalapatis <emil@etsalapatis.com>
>
> The bots are being overly picky bere, the tests pass fine and these are
> selftests anyway.
I would repost it with comment updated. I am just unsure about
README.rst part. Should that pointer about llvm 10 be removed (because
outdated) or kept as I have it?
Sebastian
prev parent reply other threads:[~2026-09-15 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 14:50 [PATCH bpf-next] selftests/bpf: Replace %pK output with 0 Sebastian Andrzej Siewior
2026-09-11 15:41 ` bot+bpf-ci
2026-09-14 9:22 ` Sebastian Andrzej Siewior
2026-09-14 23:39 ` Emil Tsalapatis
2026-09-15 6:48 ` Sebastian Andrzej Siewior [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260915064811.MrdbYUsX@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox