From: Jiri Olsa <olsajiri@gmail.com>
To: Viktor Malik <vmalik@redhat.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>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Shuah Khan <shuah@kernel.org>,
Leon Hwang <leon.hwang@linux.dev>
Subject: Re: [PATCH bpf-next v3 0/3] Always allow sleepable and fmod_ret programs on syscalls
Date: Mon, 9 Mar 2026 14:48:38 +0100 [thread overview]
Message-ID: <aa7PtlrkyHznFo-c@krava> (raw)
In-Reply-To: <cover.1773055375.git.vmalik@redhat.com>
On Mon, Mar 09, 2026 at 12:23:55PM +0100, Viktor Malik wrote:
> Both sleepable and fmod_ret programs are only allowed on selected
> functions. For convenience, the error injection list was originally
> used.
>
> When error injection is disabled, that list is empty and sleepable
> tracing programs, as well as fmod_ret programs, are effectively
> unavailable.
>
> This patch series addresses the issue by at least enabling sleepable and
> fmod_ret programs on syscalls, if error injection is disabled. More
> details on why syscalls are used can be found in [1].
>
> [1] https://lore.kernel.org/bpf/CAADnVQK6qP8izg+k9yV0vdcT-+=axtFQ2fKw7D-2Ei-V6WS5Dw@mail.gmail.com/
>
> Changes in v3:
> - Handle LoongArch (Leon)
> - Add Kumar's and Leon's acks
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
>
> Changes in v2:
> - Check "sys_" prefix instead of "sys" for powerpc syscalls (AI review)
> - Add link to the original discussion (Kumar)
> - Add explanation why arch syscall prefixes are hard-coded (Leon)
>
> Viktor Malik (3):
> bpf: Always allow sleepable programs on syscalls
> bpf: Always allow fmod_ret programs on syscalls
> selftests/bpf: Move sleepable refcounted_kptr tests to syscalls
>
> kernel/bpf/verifier.c | 85 ++++++++++++++++---
> .../selftests/bpf/progs/refcounted_kptr.c | 4 +-
> .../bpf/progs/refcounted_kptr_fail.c | 2 +-
> 3 files changed, 74 insertions(+), 17 deletions(-)
>
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-03-09 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 11:23 [PATCH bpf-next v3 0/3] Always allow sleepable and fmod_ret programs on syscalls Viktor Malik
2026-03-09 11:23 ` [PATCH bpf-next v3 1/3] bpf: Always allow sleepable " Viktor Malik
2026-03-09 11:23 ` [PATCH bpf-next v3 2/3] bpf: Always allow fmod_ret " Viktor Malik
2026-03-09 11:23 ` [PATCH bpf-next v3 3/3] selftests/bpf: Move sleepable refcounted_kptr tests to syscalls Viktor Malik
2026-03-09 13:48 ` Jiri Olsa [this message]
2026-03-09 16:40 ` [PATCH bpf-next v3 0/3] Always allow sleepable and fmod_ret programs on syscalls patchwork-bot+netdevbpf
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=aa7PtlrkyHznFo-c@krava \
--to=olsajiri@gmail.com \
--cc=alex@ghiti.fr \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=leon.hwang@linux.dev \
--cc=martin.lau@linux.dev \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.