BPF List
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Puranjay Mohan <puranjay12@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko	 <andrii@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau	 <martin.lau@kernel.org>,
	Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>,
	kernel-team@meta.com
Subject: Re: [PATCH bpf-next v3 3/6] bpf: Add KF_FORBID_SLEEP modifier for KF_ACQUIRE kfuncs
Date: Tue, 24 Feb 2026 10:17:45 -0800	[thread overview]
Message-ID: <20ec0bf67e3664eeac349dde21bdda2d3546079b.camel@gmail.com> (raw)
In-Reply-To: <CANk7y0gjg4tCcDvoK7nwcjw-w2aPtjDiJCdPvqRHS0Wvce2wiw@mail.gmail.com>

On Tue, 2026-02-24 at 15:24 +0000, Puranjay Mohan wrote:

[...]

> > - remove the following check from do_check_insn():
> > 
> >   >   if (env->cur_state->active_locks) {
> >   >       if ((insn->src_reg == BPF_REG_0 &&
> >   >            insn->imm != BPF_FUNC_spin_unlock) ||
> >   >           (insn->src_reg == BPF_PSEUDO_KFUNC_CALL &&
> >   >            (insn->off != 0 || !kfunc_spin_allowed(insn->imm)))) {
> >   >           verbose(env,
> >   >               "function calls are not allowed while holding a lock\n");
> >   >           return -EINVAL;
> >   >       }
> >   >   }
> > 
> >   Relying instead on `sleepable && !in_sleepable_context()` checks in
> >   check_kfunc_call() and check_helper_call(). (As one more refactoring patch).
> 
> But removing the above hunk has other effects, this check is not just
> about sleepable but all function calls under bpf_spin_lock. Do we want
> to relax this now?

Discussed this off-list.
The side-effect of this change is that calls to any non-sleepable
helpers / kfuncs would be allowed while holding a spin lock.
This should be fine, but probably belongs to a separate series.

  reply	other threads:[~2026-02-24 18:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 17:46 [PATCH bpf-next v3 0/6] Introduce KF_FORBID_SLEEP modifier for acquire/release kfuncs Puranjay Mohan
2026-02-23 17:46 ` [PATCH bpf-next v3 1/6] bpf: Add KF_ACQUIRE and KF_RELEASE support for iterators Puranjay Mohan
2026-02-23 19:59   ` Mykyta Yatsenko
2026-02-23 20:41   ` Eduard Zingerman
2026-02-23 17:46 ` [PATCH bpf-next v3 2/6] bpf: consolidate sleepable context error message printing Puranjay Mohan
2026-02-23 20:06   ` Mykyta Yatsenko
2026-02-23 20:27     ` Eduard Zingerman
2026-02-23 17:46 ` [PATCH bpf-next v3 3/6] bpf: Add KF_FORBID_SLEEP modifier for KF_ACQUIRE kfuncs Puranjay Mohan
2026-02-23 22:14   ` Eduard Zingerman
2026-02-24 15:24     ` Puranjay Mohan
2026-02-24 18:17       ` Eduard Zingerman [this message]
2026-02-24 19:41         ` Kumar Kartikeya Dwivedi
2026-02-23 17:46 ` [PATCH bpf-next v3 4/6] bpf: Move locking to bpf_iter_task_vma_next() Puranjay Mohan
2026-02-23 17:46 ` [PATCH bpf-next v3 5/6] bpf: Add split iteration support to task_vma iterator Puranjay Mohan
2026-02-23 17:46 ` [PATCH bpf-next v3 6/6] selftests/bpf: Add tests for split " Puranjay Mohan
2026-02-24  1:49 ` [PATCH bpf-next v3 0/6] Introduce KF_FORBID_SLEEP modifier for acquire/release kfuncs Alexei Starovoitov
2026-02-24 11:24   ` Puranjay Mohan
2026-02-24 18:00     ` Alexei Starovoitov
2026-02-24 18:55       ` Eduard Zingerman
2026-02-24 19:32         ` Alexei Starovoitov
2026-02-24 19:47           ` Puranjay Mohan
2026-02-24 19:51         ` Puranjay Mohan
2026-02-24 20:15           ` Eduard Zingerman
2026-02-24 20:20             ` Puranjay Mohan

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=20ec0bf67e3664eeac349dde21bdda2d3546079b.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=puranjay12@gmail.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