linux-kernel - Re: [PATCH v8 0/2] bpftool: Refactor config parsing and add CET symbol matching

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <91a46a61-4a9c-452b-87ae-b8fb45a2e9f2@kernel.org>
Date: Mon, 1 Sep 2025 10:58:09 +0100
From: Quentin Monnet <qmo@...nel.org>
To: chenyuan_fl@....com, ast@...nel.org, daniel@...earbox.net,
 andrii@...nel.org
Cc: yonghong.song@...ux.dev, olsajiri@...il.com, bpf@...r.kernel.org,
 linux-kernel@...r.kernel.org, chenyuan@...inos.cn
Subject: Re: [PATCH v8 0/2] bpftool: Refactor config parsing and add CET
 symbol matching

2025-09-01 10:32 UTC+0100 ~ Quentin Monnet <qmo@...nel.org>
> 2025-08-29 07:11 UTC+0100 ~ chenyuan_fl@....com
>> From: Yuan CHen <chenyuan@...inos.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.


>From Yuan's reply (please let's stick to the ML :) )

> The v7 and v8 patches are identical in code changes. The only update
> in v8 is the addition of "Ack-by" tags in commit messages.

OK thanks for confirming! No need to repost just to add the Ack tags
next time, maintainers can pick them up automatically before applying to
their tree.

Thanks,
Quentin