[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<171631323125.30783.6623831881664329095.git-patchwork-notify@kernel.org>
Date: Tue, 21 May 2024 17:40:31 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Ivan Babrou <ivan@...udflare.com>
Cc: bpf@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...udflare.com, quentin@...valent.com, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org, martin.lau@...ux.dev,
song@...nel.org, yonghong.song@...ux.dev, john.fastabend@...il.com,
kpsingh@...nel.org, sdf@...gle.com, haoluo@...gle.com, jolsa@...nel.org,
nathan@...nel.org, ndesaulniers@...gle.com, trix@...hat.com, ramasha@...com
Subject: Re: [PATCH] bpftool: un-const bpf_func_info to fix it for llvm 17 and
newer
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Mon, 20 May 2024 15:51:49 -0700 you wrote:
> LLVM 17 started treating const structs as constants:
>
> * https://github.com/llvm/llvm-project/commit/0b2d5b967d98
>
> Combined with pointer laundering via ptr_to_u64, which takes a const ptr,
> but in reality treats the underlying memory as mutable, this makes clang
> always pass zero to btf__type_by_id, which breaks full name resolution.
>
> [...]
Here is the summary with links:
- bpftool: un-const bpf_func_info to fix it for llvm 17 and newer
https://git.kernel.org/bpf/bpf-next/c/f4aba3471cfb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists