From: "Florent Revest" <florent.revest@linux.dev>
To: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
Cc: "Kumar Kartikeya Dwivedi" <memxor@gmail.com>,
"bpf" <bpf@vger.kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"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>,
"Jiri Olsa" <jolsa@kernel.org>, "KP Singh" <kpsingh@kernel.org>,
"Emil Tsalapatis" <emil@etsalapatis.com>,
"John Fastabend" <john.fastabend@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Jose Fernandez" <jose.fernandez@linux.dev>,
"LKML" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf] bpf: Keep progs alive until the trampoline image calling them is freed
Date: Sat, 12 Sep 2026 10:00:24 +0000 [thread overview]
Message-ID: <DLD90ZPDMR2Z.1YS25AGMGAB7O@linux.dev> (raw)
In-Reply-To: <CAADnVQJfvKmtD=jcOjaYaNAcfmujQm_oE7oNefTGiAAbTFj4Jg@mail.gmail.com>
On Sat Sep 12, 2026 at 12:20 AM UTC, Alexei Starovoitov wrote:
> On Wed, Sep 2, 2026 at 5:48 PM Alexei Starovoitov
> <alexei.starovoitov@gmail.com> wrote:
> >
> > Let's extend ip_after_call concept.
> > Instead of using a single NOP after the call to skip fexit progs
> > let's add NOPs in front of every invoke_bpf() including fentry and fmod_ret.
> >
> > Then on tramp destroy patch all nop-s to jmp epilogue.
> >
> > llm-s helped me realize that fentry has the same issue.
> > fentry prog A can sleep
> > while non-sleepable fentry prog B can detach and things will crash.
>
> Florent,
>
> are you planning to respin with the above fix or should I ask my clanker ?
Sorry for the wait, this week was busier than I expected! I just sent v2! :)
next prev parent reply other threads:[~2026-09-12 10:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 12:22 Florent Revest (Anthropic)
2026-08-20 15:26 ` Junseo Lim
[not found] ` <bc0edb11e07e0f6147e9c552805d0029c7aec7fc@linux.dev>
2026-08-21 7:58 ` Junseo Lim
2026-08-31 21:07 ` Florent Revest
2026-08-20 16:19 ` Leon Hwang
2026-08-30 10:40 ` Kumar Kartikeya Dwivedi
2026-08-30 13:21 ` Alexei Starovoitov
2026-08-31 2:43 ` Kumar Kartikeya Dwivedi
2026-08-31 20:58 ` Florent Revest
2026-09-02 5:57 ` Alexei Starovoitov
2026-09-02 10:15 ` Florent Revest
2026-09-02 22:06 ` Alexei Starovoitov
2026-09-02 23:25 ` Florent Revest
2026-09-03 0:48 ` Alexei Starovoitov
2026-09-12 0:20 ` Alexei Starovoitov
2026-09-12 10:00 ` Florent Revest [this message]
2026-08-31 16:40 ` Jiri Olsa
2026-08-31 20:43 ` Florent Revest
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=DLD90ZPDMR2Z.1YS25AGMGAB7O@linux.dev \
--to=florent.revest@linux.dev \
--cc=alexei.starovoitov@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=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jose.fernandez@linux.dev \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=paulmck@kernel.org \
--cc=song@kernel.org \
--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
all inboxes | Powered by JetHome®