From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next] bpf: Emit struct bpf_tcp_sock type in vmlinux BTF
Date: Tue, 02 May 2023 23:20:20 +0000 [thread overview]
Message-ID: <168306962039.20785.6836205072814420823.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230502180543.1832140-1-yhs@fb.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 2 May 2023 11:05:43 -0700 you wrote:
> In one of our internal testing, we found a case where
> - uapi struct bpf_tcp_sock is in vmlinux.h where vmlinux.h is not
> generated from the testing kernel
> - struct bpf_tcp_sock is not in vmlinux BTF
>
> The above combination caused bpf load failure as the following
> memory access
> struct bpf_tcp_sock *tcp_sock = ...;
> ... tcp_sock->snd_cwnd ...
> needs CORE relocation but the relocation cannot be resolved since
> the kernel BTF does not have corresponding type.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Emit struct bpf_tcp_sock type in vmlinux BTF
https://git.kernel.org/bpf/bpf-next/c/bf6882aebd0e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-05-02 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 18:05 [PATCH bpf-next] bpf: Emit struct bpf_tcp_sock type in vmlinux BTF Yonghong Song
2023-05-02 23:20 ` patchwork-bot+netdevbpf [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=168306962039.20785.6836205072814420823.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=yhs@fb.com \
/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;
as well as URLs for NNTP newsgroup(s).