From: Leon Hwang <leon.hwang@linux.dev>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
Emil Tsalapatis <emil@etsalapatis.com>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
Shuah Khan <shuah@kernel.org>, Sechang Lim <rhkrqnwk98@gmail.com>,
Varun R Mallya <varunrmallya@gmail.com>,
Viktor Malik <vmalik@redhat.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Fix sleepable check for tracing prog
Date: Mon, 3 Aug 2026 09:41:40 +0800 [thread overview]
Message-ID: <b2fe4e37-d210-4c58-9eda-185834af7338@linux.dev> (raw)
In-Reply-To: <CAEf4BzbjmW0e6DqFLUAyV+m_usHSkHpux3AdS72bJtsmYQC_LA@mail.gmail.com>
On 31/7/26 23:21, Andrii Nakryiko wrote:
> On Thu, Jul 30, 2026 at 10:20 PM Leon Hwang <leon.hwang@linux.dev> wrote:
>>
>> On 31/7/26 08:07, Andrii Nakryiko wrote:
>>> On Sat, Jul 25, 2026 at 6:27 AM Leon Hwang <leon.hwang@linux.dev> wrote:
>>>>
>>>> When CONFIG_FUNCTION_ERROR_INJECTION is disabled, a sleepable tracing prog
>>>> is allowed to attach to '__x64_'-alike prefix symbols.
>>>>
>>>> It is because the verifier does not verify whether the symbol is a kernel
>>>> function or a bpf prog. That said, a sleepable tracing prog is allowed to
>>>> attach to a bpf prog target whose name has '__x64_'-alike prefix.
>>>>
>>>> For example, a sleepable fentry prog attaches to a '__x64_sys_nop' XDP
>>>
>>> we do have addr, so we should be able to distinguish between attaching
>>> to kernel function vs BPF program, no?
>>
>>
>> Yes, we can distinguish a bpf prog from a kernel function by addr.
>>
>> I'd prefer passing 'tgt_prog' to btf_id_allow_sleepable() as a simple
>> change.
>>
>
> I don't think there is a need for new tgt_prog argument, we can just
> check that supplied btf is not kernel/module BTF (see btf_is_kernel())
>
Makes sense.
Will use btf_is_kernel().
Thanks,
Leon
prev parent reply other threads:[~2026-08-03 1:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 13:26 [PATCH bpf-next v2 0/2] bpf: Fix sleepable check for tracing prog Leon Hwang
2026-07-25 13:26 ` [PATCH bpf-next v2 1/2] " Leon Hwang
2026-07-25 13:26 ` [PATCH bpf-next v2 2/2] selftests/bpf: Verify rejection of sleepable " Leon Hwang
2026-07-31 0:07 ` [PATCH bpf-next v2 0/2] bpf: Fix sleepable check for " Andrii Nakryiko
2026-07-31 5:20 ` Leon Hwang
2026-07-31 15:21 ` Andrii Nakryiko
2026-08-03 1:41 ` Leon Hwang [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=b2fe4e37-d210-4c58-9eda-185834af7338@linux.dev \
--to=leon.hwang@linux.dev \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rhkrqnwk98@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=varunrmallya@gmail.com \
--cc=vmalik@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).