From: Quentin Monnet <qmo@kernel.org>
To: chenyuan_fl@163.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org
Cc: 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: Mon, 1 Sep 2025 10:32:23 +0100 [thread overview]
Message-ID: <b245b389-e057-40d3-8e2a-7cce5c290c63@kernel.org> (raw)
In-Reply-To: <20250829061107.23905-1-chenyuan_fl@163.com>
2025-08-29 07:11 UTC+0100 ~ chenyuan_fl@163.com
> 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
>
> Changed in PATCH v4:
> * Refactor repeated code into a function.
> * Add detection for the x86 architecture.
>
> Changed int PATH v5:
> * Remove detection for the x86 architecture.
>
> Changed in PATCH v6:
> * Add new helper patch (1/2) to refactor kernel config reading
> * Use the new read_kernel_config() in CET symbol matching (2/2) to check CONFIG_X86_KERNEL_IBT
>
> Changed in PATCH v7:
> * Display actual kprobe attachment addresses instead of symbol addresses
Hi Yuan,
Is there any difference between v7 and v8 of your series? They seem
identical, from what I can see.
Quentin
next prev parent reply other threads:[~2025-09-01 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 6:11 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 ` Quentin Monnet [this message]
2025-09-01 9:58 ` [PATCH v8 0/2] bpftool: Refactor config parsing and add CET symbol matching Quentin Monnet
2025-09-02 15:30 ` 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=b245b389-e057-40d3-8e2a-7cce5c290c63@kernel.org \
--to=qmo@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=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®