From: Tao Chen <chen.dylane@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
patchwork-bot+netdevbpf@kernel.org
Cc: qmo@kernel.org, ast@kernel.org, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpftool: Remove llvm-strip from Makefile
Date: Thu, 26 Sep 2024 00:25:25 +0800 [thread overview]
Message-ID: <8bc57566-2867-49f5-8b66-7c5f32c1a0c8@gmail.com> (raw)
In-Reply-To: <4f58b093-ca1f-426a-8102-4b00ccaf4973@iogearbox.net>
在 2024/9/25 18:32, Daniel Borkmann 写道:
> On 9/25/24 11:50 AM, patchwork-bot+netdevbpf@kernel.org wrote:
>> Hello:
>>
>> This patch was applied to bpf/bpf-next.git (master)
>> by Daniel Borkmann <daniel@iogearbox.net>:
>>
>> On Wed, 25 Sep 2024 00:52:02 +0800 you wrote:
>>> As Quentin and Andrri said [0], bpftool gen object strips
>>> out DWARF already, so remove the repeat operation.
>>>
>>> [0] https://github.com/libbpf/bpftool/issues/161
>>>
>>> Suggested-by: Andrii Nakryiko <andrii@kernel.org>
>>> Suggested-by: Quentin Monnet <qmo@kernel.org>
>>> Signed-off-by: Tao Chen <chen.dylane@gmail.com>
>>>
>>> [...]
> I'll toss this shortly from the tree again, this missed that bpftool gen
> object call
> needs to strip out dwarf.
Hi Daniel, i saw linker_sanity_check_elf will ignore the dwarf sec,
which means bpftool gen object will strip, is my understanding correct?
static int linker_sanity_check_elf(struct src_obj *obj)
{
...
if (is_dwarf_sec_name(sec->sec_name))
continue;
...
}
>>> Here is the summary with links:
>>> - [bpf-next] bpftool: Remove llvm-strip from Makefile
>>> https://git.kernel.org/bpf/bpf-next/c/25bfc6333e32
>>>
>>> You are awesome, thank you!
--
Best Regards
Dylane Chen
prev parent reply other threads:[~2024-09-25 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 16:52 [PATCH bpf-next] bpftool: Remove llvm-strip from Makefile Tao Chen
2024-09-24 18:35 ` Quentin Monnet
2024-09-25 9:50 ` patchwork-bot+netdevbpf
2024-09-25 10:32 ` Daniel Borkmann
2024-09-25 16:25 ` Tao Chen [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=8bc57566-2867-49f5-8b66-7c5f32c1a0c8@gmail.com \
--to=chen.dylane@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=qmo@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