From: Yonghong Song <yonghong.song@linux.dev>
To: chenyuan_fl@163.com, olsajiri@gmail.com
Cc: aef2617b-ce03-4830-96a7-39df0c93aaad@kernel.org,
andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
chenyuan@kylinos.cn, daniel@iogearbox.net,
linux-kernel@vger.kernel.org, qmo@kernel.org
Subject: Re: [PATCH v7 2/2] bpftool: Add CET-aware symbol matching for x86_64 architectures
Date: Mon, 25 Aug 2025 13:39:33 -0700 [thread overview]
Message-ID: <aed65fc2-8d34-4407-a049-fdc1ff5111ec@linux.dev> (raw)
In-Reply-To: <20250825022002.13760-3-chenyuan_fl@163.com>
On 8/24/25 7:20 PM, chenyuan_fl@163.com wrote:
> From: Yuan Chen <chenyuan@kylinos.cn>
>
> Adjust symbol matching logic to account for Control-flow Enforcement
> Technology (CET) on x86_64 systems. CET prefixes functions with
> a 4-byte 'endbr' instruction, shifting the actual hook entry point to
> symbol + 4.
>
> Signed-off-by: Yuan Chen <chenyuan@kylinos.cn>
Acked-by: Yonghong Song <yonghong.song@linux.dev>
next prev parent reply other threads:[~2025-08-25 20:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 2:20 [PATCH v5] bpftool: Add CET-aware symbol matching for x86_64 architectures chenyuan_fl
2025-07-23 10:24 ` Quentin Monnet
2025-07-23 13:08 ` Jiri Olsa
2025-07-23 15:52 ` Yonghong Song
2025-08-15 2:52 ` [PATCH 0/2] bpftool: Refactor config parsing and add CET symbol matching chenyuan_fl
2025-08-15 2:52 ` [PATCH v6 1/2] bpftool: Refactor kernel config reading into common helper chenyuan_fl
2025-08-15 2:52 ` [PATCH v6 2/2] bpftool: Add CET-aware symbol matching for x86_64 architectures chenyuan_fl
2025-08-18 9:55 ` Jiri Olsa
2025-08-25 2:20 ` [PATCH v7 0/2] bpftool: Refactor config parsing and add CET symbol matching chenyuan_fl
2025-08-25 2:20 ` [PATCH v7 1/2] bpftool: Refactor kernel config reading into common helper chenyuan_fl
2025-08-25 20:29 ` Yonghong Song
2025-08-25 2:20 ` [PATCH v7 2/2] bpftool: Add CET-aware symbol matching for x86_64 architectures chenyuan_fl
2025-08-25 20:39 ` Yonghong Song [this message]
2025-08-25 22:44 ` [PATCH v7 0/2] bpftool: Refactor config parsing and add CET symbol matching Jiri Olsa
2025-08-27 21:53 ` Andrii Nakryiko
2025-08-28 21:50 ` Quentin Monnet
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=aed65fc2-8d34-4407-a049-fdc1ff5111ec@linux.dev \
--to=yonghong.song@linux.dev \
--cc=aef2617b-ce03-4830-96a7-39df0c93aaad@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 \
/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.