public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Hwang <leon.hwang@linux.dev>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	bot+bpf-ci@kernel.org, Menglong Dong <menglong8.dong@gmail.com>
Cc: mykyta.yatsenko5@gmail.com, bpf@vger.kernel.org, ast@kernel.org,
	andrii@kernel.org, daniel@iogearbox.net, kafai@meta.com,
	kernel-team@meta.com, eddyz87@gmail.com, yatsenko@meta.com,
	martin.lau@kernel.org, yonghong.song@linux.dev, clm@meta.com,
	ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next v3 2/4] bpf: Verifier support for sleepable raw tracepoint programs
Date: Thu, 12 Mar 2026 13:50:08 +0800	[thread overview]
Message-ID: <46583200-ee0e-41dd-a0a9-8944ad710a9a@linux.dev> (raw)
In-Reply-To: <CAP01T77gknuNiiVKny-cThb6b-dFxGPmPKx1eMryLoN2AkHo8w@mail.gmail.com>

On 12/3/26 07:07, Kumar Kartikeya Dwivedi wrote:
> On Wed, 11 Mar 2026 at 19:53, <bot+bpf-ci@kernel.org> wrote:
>>
>>> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
>>> --- a/kernel/bpf/verifier.c
>>> +++ b/kernel/bpf/verifier.c
>>
>> [ ... ]
>>
>>> @@ -25435,6 +25441,7 @@ static bool can_be_sleepable(struct bpf_prog *prog)
>>>               case BPF_MODIFY_RETURN:
>>>               case BPF_TRACE_ITER:
>>>               case BPF_TRACE_FSESSION:
>>> +             case BPF_TRACE_RAW_TP:
>>>                       return true;
>>>               default:
>>>                       return false;
>>> @@ -25464,7 +25471,7 @@ struct bpf_attach_target_info tgt_info = {};
>>>       }
>>>
>>>       if (prog->sleepable && !can_be_sleepable(prog)) {
>>> -             verbose(env, "Only fentry/fexit/fmod_ret, lsm, iter, uprobe, and struct_ops programs can be sleepable\n");
>>> +             verbose(env, "Only fentry/fexit/fmod_ret, lsm, iter, uprobe, struct_ops, and raw_tp programs can be sleepable\n");
>>
>> The updated error message adds raw_tp but still omits fsession,
>> which is listed in can_be_sleepable() just above. Should this
>> read "fentry/fexit/fmod_ret/fsession, lsm, iter, uprobe,
>> struct_ops, and raw_tp"?
>>
> 
> We can ignore AI for now, Leon has a change for this.
> 
Just to confirm the change: is it
https://lore.kernel.org/bpf/20260303150639.85007-2-leon.hwang@linux.dev/?

If yes, it is to add "fsession" to the verbose log message in
check_get_func_ip(). Then, the AI review is correct: "fsession" was
missing here.

After searching for "fexit" in verifier.c, "FENTRY/FEXIT" can be updated
to "FENTRY/FEXIT/FSESSION" in bpf_check_attach_target(), and "fsession"
is missing in some comments. I'm not sure whether it is worth a patch to
do such cleanup work.

cc Menglong

Thanks,
Leon


  reply	other threads:[~2026-03-12  5:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 18:22 [PATCH bpf-next v3 0/4] bpf: Add support for sleepable raw tracepoint programs Mykyta Yatsenko
2026-03-11 18:22 ` [PATCH bpf-next v3 1/4] bpf: Add sleepable execution path for " Mykyta Yatsenko
2026-03-11 19:25   ` Emil Tsalapatis
2026-03-11 23:39   ` Puranjay Mohan
2026-03-12 20:51   ` Andrii Nakryiko
2026-03-11 18:22 ` [PATCH bpf-next v3 2/4] bpf: Verifier support for sleepable " Mykyta Yatsenko
2026-03-11 18:49   ` Emil Tsalapatis
2026-03-11 18:53   ` bot+bpf-ci
2026-03-11 23:07     ` Kumar Kartikeya Dwivedi
2026-03-12  5:50       ` Leon Hwang [this message]
2026-03-12  6:21         ` Menglong Dong
2026-03-12  6:43           ` Leon Hwang
2026-03-11 23:08   ` Kumar Kartikeya Dwivedi
2026-03-11 23:40   ` Puranjay Mohan
2026-03-12 20:59   ` Andrii Nakryiko
2026-03-11 18:22 ` [PATCH bpf-next v3 3/4] libbpf: Add tp_btf.s section handler for sleepable raw tracepoints Mykyta Yatsenko
2026-03-11 18:54   ` Emil Tsalapatis
2026-03-11 23:40   ` Puranjay Mohan
2026-03-12 20:59   ` Andrii Nakryiko
2026-03-11 18:22 ` [PATCH bpf-next v3 4/4] selftests/bpf: Add tests for sleepable raw tracepoint programs Mykyta Yatsenko
2026-03-11 19:12   ` Emil Tsalapatis
2026-03-11 23:41   ` Puranjay Mohan
2026-03-12 21:03   ` Andrii Nakryiko

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=46583200-ee0e-41dd-a0a9-8944ad710a9a@linux.dev \
    --to=leon.hwang@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bot+bpf-ci@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=clm@meta.com \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=kafai@meta.com \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    --cc=menglong8.dong@gmail.com \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=yatsenko@meta.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