What about enabling CONFIG_IKHEADERS in master?
Hi, I have recently built a few custom kernels (locally, not packaged), and I quickly ran into an issue with eBPF not able to find kernel headers (or finding the wrong ones). The kernel headers can be packed into a kernel module (kheaders.ko) if CONFIG_IKHEADERS=m. Would anyone object to enabling this option on master branch? Cheers Petr T
Hi, On 16. 03. 23, 10:08, Petr Tesařík wrote:
I have recently built a few custom kernels (locally, not packaged), and I quickly ran into an issue with eBPF not able to find kernel headers (or finding the wrong ones). The kernel headers can be packed into a kernel module (kheaders.ko) if CONFIG_IKHEADERS=m.
Can you elaborate how exactly this helps? E.g. opposing to having kernel-devel/source installed?
Would anyone object to enabling this option on master branch?
What's the size of the tar/module? In any way, you should open a bug for something like this. thanks, -- js suse labs
Hi Jiri,
On Thu, 16 Mar 2023 10:14:59 +0100
Jiri Slaby
Hi,
On 16. 03. 23, 10:08, Petr Tesařík wrote:
I have recently built a few custom kernels (locally, not packaged), and I quickly ran into an issue with eBPF not able to find kernel headers (or finding the wrong ones). The kernel headers can be packed into a kernel module (kheaders.ko) if CONFIG_IKHEADERS=m.
Can you elaborate how exactly this helps? E.g. opposing to having kernel-devel/source installed?
On a second thought, you're right. There's no benefit the kernel is built as a package. I was bisecting a regression, so I wasn't going through all the hassle of RPM packaging, but then it makes more sense I remember to enable this option for such builds.
Would anyone object to enabling this option on master branch?
What's the size of the tar/module?
It's approx. 4 MiB, but like I wrote above, forget about it. Sorry for the fuss, Petr T
On Thu, Mar 16, 2023 at 10:08:23AM +0100, Petr Tesařík wrote:
I have recently built a few custom kernels (locally, not packaged), and I quickly ran into an issue with eBPF not able to find kernel headers (or finding the wrong ones). The kernel headers can be packed into a kernel module (kheaders.ko) if CONFIG_IKHEADERS=m.
Would anyone object to enabling this option on master branch?
My first thought was "Wait, I thought I did enable this when the option appeared." :-) Apparently I found some reason not to but I'm not sure what it was. Perhaps the concern of kernel size and lack of clear and obvious use case. So I suppose I left it for later if someone comes asks for it to be enabled because he needs it. (Which might have just happened.) Michal
On Thu, 16 Mar 2023 10:37:03 +0100
Michal Kubecek
On Thu, Mar 16, 2023 at 10:08:23AM +0100, Petr Tesařík wrote:
I have recently built a few custom kernels (locally, not packaged), and I quickly ran into an issue with eBPF not able to find kernel headers (or finding the wrong ones). The kernel headers can be packed into a kernel module (kheaders.ko) if CONFIG_IKHEADERS=m.
Would anyone object to enabling this option on master branch?
My first thought was "Wait, I thought I did enable this when the option appeared." :-) Apparently I found some reason not to but I'm not sure what it was.
As stated in the other sub-thread started by Jiří, there is no need for it in a distribution kernel. Self-built kernels usually diverge anyway, so they may also diverge in this option. Now, it's at least documented here why it's disabled. Petr T
participants (3)
-
Jiri Slaby -
Michal Kubecek -
Petr Tesařík