| 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
| ||
|
Date: Thu, 17 Nov 2022 22:15:52 +0800
From: Rong Tao <rtoax@...mail.com>
To: andrii.nakryiko@...il.com
Cc: andrii@...nel.org, ast@...nel.org, bpf@...r.kernel.org,
daniel@...earbox.net, dxu@...uu.xyz, haoluo@...gle.com,
john.fastabend@...il.com, jolsa@...nel.org, kpsingh@...nel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
lkp@...el.com, lorenzo@...nel.org, martin.lau@...ux.dev,
memxor@...il.com, mykolal@...com, rongtao@...tc.cn,
rtoax@...mail.com, sdf@...gle.com, shuah@...nel.org,
song@...nel.org, yhs@...com
Subject: Re: Re: [PATCH bpf-next] selftests/bpf: Fix error undeclared identifier 'NF_NAT_MANIP_SRC'
First of all, thank you all for your suggestions on this compilation
issue.
> It does break CI ([0]). We could use BPF CO-RE and ___suffix rule to
> avoid this. But we can also say that selftests/bpf/config{,<arch>} has
> to be used by bots that want to build BPF selftests.
>
> [0] https://github.com/kernel-patches/bpf/actions/runs/3446651033/jobs/5752592868
I try to use bpf_core_enum_value_exists() and bpf_core_enum_value(), However,
as far as my knowledge is concerned, I have to redefine a NF_NAT_MANIP_SRC
enumeration, but this would conflict with the situation where there is no
secondary compilation problem. How do I fix this with CO-RE, it seems that
there is no similar CO-RE+ __suffix solution for enumerations in selftests.
Can you give me some tips or help me?
Powered by blists - more mailing lists