netdev - Re: [PATCH bpf-next v8 00/10] Introduce unstable CT lookup helpers

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] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 19 Feb 2022 08:39:15 +0100
From:   Alexander Egorenkov <egorenar@...ux.ibm.com>
To:     memxor@...il.com
Cc:     egorenar@...ux.ibm.com
Subject: Re: [PATCH bpf-next v8 00/10] Introduce unstable CT lookup helpers

Hi Kartikeya,

sorry if i wasn't clear in my first message but just to be sure
we have no misunderstandings :)

.BTF sections work on s390x with linux-next and nf_conntrack as well if
the corresponding .BTF section is a part of the kernel module itself.
I tested it myself by building a linux-next kernel and testing it with a
KVM guest, i'm able to load nf_conntrack and it works.

In contrast, in the case where the corresponding .BTF section is separate
from the kernel module nf_conntrack, it fails with the message i
provided in the first email.

Therefore, my question is, does BTF for kernel modules work if the
corresponding BTF section is NOT a part of the kernel module but instead
is stored within the corresponding debuginfo file
/usr/lib/debug/lib/modules/*/kernel/net/netfilter/nf_conntrack.ko.debug ?

Thanks
Regards
Alex