From: patchwork-bot+netdevbpf@kernel.org
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, davem@davemloft.net, dsahern@kernel.org,
tglx@linutronix.de, mingo@redhat.com, jiang.biao@linux.dev,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v13 00/13] bpf: fsession support
Date: Sun, 25 Jan 2026 03:00:22 +0000 [thread overview]
Message-ID: <176931002209.3419928.12789468285524749357.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260124062008.8657-1-dongml2@chinatelecom.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 24 Jan 2026 14:19:55 +0800 you wrote:
> overall
> -------
> Sometimes, we need to hook both the entry and exit of a function with
> TRACING. Therefore, we need define a FENTRY and a FEXIT for the target
> function, which is not convenient.
>
> Therefore, we add a tracing session support for TRACING. Generally
> speaking, it's similar to kprobe session, which can hook both the entry
> and exit of a function with a single BPF program.
>
> [...]
Here is the summary with links:
- [bpf-next,v13,01/13] bpf: add fsession support
https://git.kernel.org/bpf/bpf-next/c/2d419c44658f
- [bpf-next,v13,02/13] bpf: use the least significant byte for the nr_args in trampoline
https://git.kernel.org/bpf/bpf-next/c/f1b56b3cbdb2
- [bpf-next,v13,03/13] bpf: change prototype of bpf_session_{cookie,is_return}
https://git.kernel.org/bpf/bpf-next/c/8fe4dc4f6456
- [bpf-next,v13,04/13] bpf: support fsession for bpf_session_is_return
https://git.kernel.org/bpf/bpf-next/c/27d89baa6da8
- [bpf-next,v13,05/13] bpf: support fsession for bpf_session_cookie
https://git.kernel.org/bpf/bpf-next/c/eeee4239dbb1
- [bpf-next,v13,06/13] bpf,x86: introduce emit_store_stack_imm64() for trampoline
https://git.kernel.org/bpf/bpf-next/c/37c7ba1b39c4
- [bpf-next,v13,07/13] bpf,x86: add fsession support for x86_64
https://git.kernel.org/bpf/bpf-next/c/98770bd4e6df
- [bpf-next,v13,08/13] libbpf: add fsession support
https://git.kernel.org/bpf/bpf-next/c/257c43688b14
- [bpf-next,v13,09/13] bpftool: add fsession support
https://git.kernel.org/bpf/bpf-next/c/85fc4be6d811
- [bpf-next,v13,10/13] selftests/bpf: add testcases for fsession
https://git.kernel.org/bpf/bpf-next/c/f7afef5617b6
- [bpf-next,v13,11/13] selftests/bpf: test bpf_get_func_* for fsession
https://git.kernel.org/bpf/bpf-next/c/a5533a6eaa5b
- [bpf-next,v13,12/13] selftests/bpf: add testcases for fsession cookie
https://git.kernel.org/bpf/bpf-next/c/8909b3fb23e2
- [bpf-next,v13,13/13] selftests/bpf: test fsession mixed with fentry and fexit
https://git.kernel.org/bpf/bpf-next/c/cb4bfacfb011
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-25 3:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 6:19 [PATCH bpf-next v13 00/13] bpf: fsession support Menglong Dong
2026-01-24 6:19 ` [PATCH bpf-next v13 01/13] bpf: add " Menglong Dong
2026-01-24 6:19 ` [PATCH bpf-next v13 02/13] bpf: use the least significant byte for the nr_args in trampoline Menglong Dong
2026-01-24 6:19 ` [PATCH bpf-next v13 03/13] bpf: change prototype of bpf_session_{cookie,is_return} Menglong Dong
2026-01-24 6:19 ` [PATCH bpf-next v13 04/13] bpf: support fsession for bpf_session_is_return Menglong Dong
2026-01-24 6:20 ` [PATCH bpf-next v13 05/13] bpf: support fsession for bpf_session_cookie Menglong Dong
2026-01-24 6:20 ` [PATCH bpf-next v13 06/13] bpf,x86: introduce emit_store_stack_imm64() for trampoline Menglong Dong
2026-01-24 6:20 ` [PATCH bpf-next v13 07/13] bpf,x86: add fsession support for x86_64 Menglong Dong
2026-01-24 6:20 ` [PATCH bpf-next v13 08/13] libbpf: add fsession support Menglong Dong
2026-01-24 6:20 ` [PATCH bpf-next v13 09/13] bpftool: " Menglong Dong
2026-01-24 6:20 ` [PATCH bpf-next v13 10/13] selftests/bpf: add testcases for fsession Menglong Dong
2026-01-24 6:20 ` [PATCH bpf-next v13 11/13] selftests/bpf: test bpf_get_func_* " Menglong Dong
2026-01-24 6:20 ` [PATCH bpf-next v13 12/13] selftests/bpf: add testcases for fsession cookie Menglong Dong
2026-01-24 6:20 ` [PATCH bpf-next v13 13/13] selftests/bpf: test fsession mixed with fentry and fexit Menglong Dong
2026-01-25 3:00 ` patchwork-bot+netdevbpf [this message]
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=176931002209.3419928.12789468285524749357.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hpa@zytor.com \
--cc=jiang.biao@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=menglong8.dong@gmail.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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