From: patchwork-bot+netdevbpf@kernel.org
To: chenyuan <chenyuan_fl@163.com>
Cc: qmo@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, yonghong.song@linux.dev, olsajiri@gmail.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
chenyuan@kylinos.cn
Subject: Re: [PATCH v8 0/2] bpftool: Refactor config parsing and add CET symbol matching
Date: Tue, 02 Sep 2025 15:30:07 +0000 [thread overview]
Message-ID: <175682700752.343659.7302091706748568937.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250829061107.23905-1-chenyuan_fl@163.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 29 Aug 2025 07:11:05 +0100 you wrote:
> From: Yuan CHen <chenyuan@kylinos.cn>
>
> 1. **Refactor kernel config parsing**
> - Moves duplicate config file handling from feature.c to common.c
> - Keeps all existing functionality while enabling code reuse
>
> 2. **Add CET-aware symbol matching**
> - Adjusts kprobe hook detection for x86_64 CET (endbr32/64 prefixes)
> - Matches symbols at both original and CET-adjusted addresses
>
> [...]
Here is the summary with links:
- [v8,1/2] bpftool: Refactor kernel config reading into common helper
https://git.kernel.org/bpf/bpf-next/c/70f32a10ad42
- [v8,2/2] bpftool: Add CET-aware symbol matching for x86_64 architectures
https://git.kernel.org/bpf/bpf-next/c/6417ca85305e
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:[~2025-09-02 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 6:11 [PATCH v8 0/2] bpftool: Refactor config parsing and add CET symbol matching chenyuan_fl
2025-08-29 6:11 ` [PATCH v8 1/2] bpftool: Refactor kernel config reading into common helper chenyuan_fl
2025-08-29 6:11 ` [PATCH v8 2/2] bpftool: Add CET-aware symbol matching for x86_64 architectures chenyuan_fl
2025-09-01 9:32 ` [PATCH v8 0/2] bpftool: Refactor config parsing and add CET symbol matching Quentin Monnet
2025-09-01 9:58 ` Quentin Monnet
2025-09-02 15:30 ` 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=175682700752.343659.7302091706748568937.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenyuan@kylinos.cn \
--cc=chenyuan_fl@163.com \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=qmo@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 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.