From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: Quentin Monnet <qmo@kernel.org>,
bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com
Cc: Mykyta Yatsenko <yatsenko@meta.com>
Subject: Re: [PATCH bpf-next v2] bpftool: Allow explicitly skip llvm dependency
Date: Thu, 29 Jan 2026 17:50:14 +0000 [thread overview]
Message-ID: <416c6ad9-152e-486c-b169-123c06d398e9@gmail.com> (raw)
In-Reply-To: <2b6f4cd9-ff0f-4a91-90ef-8d8e6812f80f@kernel.org>
On 1/29/26 17:34, Quentin Monnet wrote:
> 2026-01-28 23:34 UTC+0000 ~ Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
>> From: Mykyta Yatsenko <yatsenko@meta.com>
>>
>> BPF selftests depend on the bpftool. In some environments we may link
>> bpftool to llvm dynamically and then try to run somewhere where llvm
>> library is not available.
>> It's simpler to avoid llvm linking altogether in those cases, this
>> change allows to do it.
>>
>> Signed-off-by: Mykyta Yatsenko <yatsenko@meta.com>
>
> Hi Mykyta, thanks for the patch. Do you have any other solution to make
> it work on your environment? We've been rejecting similar changes in the
> past, because we don't want to encourage people to strip away the
> disassembler when shipping bpftool [0], so I'd rather avoid adding this
> if you have another workaround available.
>
> [0] https://lore.kernel.org/bpf/9ffd4b6b-0073-cfef-5889-cb4d0b838f8e@iogearbox.net/
we have a workaround, a little ugly, but we can improve that,
anyways, I'm happy to abandon this change.
next prev parent reply other threads:[~2026-01-29 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 23:34 [PATCH bpf-next v2] bpftool: Allow explicitly skip llvm dependency Mykyta Yatsenko
2026-01-29 17:34 ` Quentin Monnet
2026-01-29 17:50 ` Mykyta Yatsenko [this message]
2026-01-30 20:46 ` Andrii Nakryiko
2026-01-30 23:48 ` Quentin Monnet
2026-02-04 1:17 ` Andrii Nakryiko
2026-02-04 14:24 ` Quentin Monnet
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=416c6ad9-152e-486c-b169-123c06d398e9@gmail.com \
--to=mykyta.yatsenko5@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=qmo@kernel.org \
--cc=yatsenko@meta.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