From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: Martin KaFai Lau <martin.lau@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
bpf@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: WARN: multiple IDs found for 'nf_conn': 92168, 117897 - using 92168
Date: Tue, 4 Oct 2022 08:34:15 -0700 [thread overview]
Message-ID: <20221004083415.00de247f@kernel.org> (raw)
In-Reply-To: <20221004144603.obymbke3oarhgnnz@kashmir.localdomain>
On Tue, 4 Oct 2022 08:46:03 -0600 Daniel Xu wrote:
> > WARN: multiple IDs found for 'nf_conn': 92168, 117897 - using 92168
> > WARN: multiple IDs found for 'nf_conn': 92168, 121226 - using 92168
>
> I believe this is now-fixed pahole bug. See:
> https://lore.kernel.org/bpf/20220907023559.22juhtyl3qh2gsym@kashmir.localdomain/
>
> That being said, I didn't manage to find a pahole commit that directly
> addresses the issue, so maybe upgrading pahole perturbed enough things
> for this warning to go away?
>
> If the warning is back on pahole master I can take another look.
From-the-source pahole fixes it, thanks!
next prev parent reply other threads:[~2022-10-04 15:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 2:05 objtool: bpf_dispatcher_xdp+0xa0: data relocation to !ENDBR: Jakub Kicinski
2022-10-04 4:49 ` WARN: multiple IDs found for 'nf_conn': 92168, 117897 - using 92168 Jakub Kicinski
2022-10-04 6:42 ` Jiri Olsa
2022-10-04 14:25 ` Jakub Kicinski
2022-10-05 9:45 ` Jiri Olsa
2022-10-05 15:44 ` Jakub Kicinski
2022-10-05 16:18 ` Jakub Kicinski
2022-10-05 20:07 ` Jiri Olsa
2022-10-13 15:05 ` Jakub Kicinski
2022-10-13 21:55 ` Jiri Olsa
2022-10-13 22:12 ` Jiri Olsa
2022-10-13 22:24 ` Andrii Nakryiko
2022-10-14 6:47 ` Jiri Olsa
2022-10-14 17:17 ` Alan Maguire
2022-10-16 13:07 ` Jiri Olsa
2022-10-21 18:18 ` Andrii Nakryiko
2022-10-21 21:34 ` Jiri Olsa
2022-10-22 5:36 ` Jakub Kicinski
2022-10-23 1:18 ` Alexei Starovoitov
2022-10-24 18:21 ` Jakub Kicinski
2022-10-04 14:46 ` Daniel Xu
2022-10-04 15:34 ` Jakub Kicinski [this message]
2022-10-18 15:11 ` Christian Borntraeger
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=20221004083415.00de247f@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=jolsa@kernel.org \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.