All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Hwang <leon.hwang@linux.dev>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: Viktor Malik <vmalik@redhat.com>,
	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>,
	Jiri Olsa <jolsa@kernel.org>, 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>
Subject: Re: [PATCH bpf-next 0/3] Always allow sleepable and fmod_ret programs on syscalls
Date: Fri, 6 Mar 2026 10:16:31 +0800	[thread overview]
Message-ID: <e7316548-8f90-4569-8ef9-e7a14a5ccd16@linux.dev> (raw)
In-Reply-To: <CAP01T77dvSCyGq4L6XFS3uMeB7dTwCRvbePL-mnbEHDU7xvm=A@mail.gmail.com>

On 6/3/26 10:14, Kumar Kartikeya Dwivedi wrote:
> On Fri, 6 Mar 2026 at 03:04, Leon Hwang <leon.hwang@linux.dev> wrote:
>>
>> Hi Viktor,
>>
>> On 5/3/26 23:25, 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.
>>>
>>
>> Could you please explain more about the purpose in cover letter?
>>
>> I'm curious about enabling fmod_ret programs on syscalls, as they are
>> able to modify the retval of syscalls.
> 
> It was already discussed at length here:
> https://lore.kernel.org/bpf/CAADnVQJ4PU7bCb5XO9+zMZhLRSdbCKwxG6Rtojh2Rc3UZ8H43Q@mail.gmail.com/
> 

Thanks for pointing this out.

Thanks,
Leon

> I think the next version could include a link to the previous thread
> in the cover letter for posterity.
> 
>>
>> Thanks,
>> 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                         | 79 +++++++++++++++----
>>>  .../selftests/bpf/progs/refcounted_kptr.c     |  4 +-
>>>  .../bpf/progs/refcounted_kptr_fail.c          |  2 +-
>>>  3 files changed, 68 insertions(+), 17 deletions(-)
>>>
>>
>>


  reply	other threads:[~2026-03-06  2:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 15:25 [PATCH bpf-next 0/3] Always allow sleepable and fmod_ret programs on syscalls Viktor Malik
2026-03-05 15:25 ` [PATCH bpf-next 1/3] bpf: Always allow sleepable " Viktor Malik
2026-03-05 16:07   ` bot+bpf-ci
2026-03-06  2:02     ` Kumar Kartikeya Dwivedi
2026-03-06  6:23       ` Viktor Malik
2026-03-06  2:05   ` Leon Hwang
2026-03-06  7:09     ` Viktor Malik
2026-03-06  7:41       ` Leon Hwang
2026-03-06  8:38         ` Viktor Malik
2026-03-05 15:25 ` [PATCH bpf-next 2/3] bpf: Always allow fmod_ret " Viktor Malik
2026-03-05 15:25 ` [PATCH bpf-next 3/3] selftests/bpf: Move sleepable refcounted_kptr tests to syscalls Viktor Malik
2026-03-06  2:04 ` [PATCH bpf-next 0/3] Always allow sleepable and fmod_ret programs on syscalls Leon Hwang
2026-03-06  2:14   ` Kumar Kartikeya Dwivedi
2026-03-06  2:16     ` Leon Hwang [this message]
2026-03-06  6:26       ` Viktor Malik

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=e7316548-8f90-4569-8ef9-e7a14a5ccd16@linux.dev \
    --to=leon.hwang@linux.dev \
    --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=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --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.