Re: [PATCH v3 1/2] Provide in-kernel headers for making it easy to extend the kernel

From: Joel Fernandes
Date: Thu Feb 28 2019 - 14:10:43 EST


On Thu, Feb 28, 2019 at 05:04:59PM +0100, Dietmar Eggemann wrote:
[...] ^
> kernel/kheaders_data.h:1:1: note: in expansion of macro âKH_MAGIC_ENDâ
> KH_MAGIC_END;
> ^~~~~~~~~~~~
> kernel/kheaders.c: In function âikheaders_read_currentâ:
> kernel/kheaders.c:38:12: error: âkernel_headers_dataâ undeclared (first use
> in this function); did you mean âkernel_headers_data_sizeâ?
> kernel_headers_data + KH_MAGIC_SIZE,
> ^~~~~~~~~~~~~~~~~~~
> kernel_headers_data_size
> kernel/kheaders.c:38:12: note: each undeclared identifier is reported only
> once for each function it appears in
> kernel/kheaders.c: In function âikheaders_initâ:
> kernel/kheaders.c:31:10: error: âkernel_headers_dataâ undeclared (first use
> in this function); did you mean âkernel_headers_data_sizeâ?
> (sizeof(kernel_headers_data) - 1 - KH_MAGIC_SIZE * 2)
> ^
> kernel/kheaders.c:57:23: note: in expansion of macro
> âkernel_headers_data_sizeâ
> proc_set_size(entry, kernel_headers_data_size);
> ^~~~~~~~~~~~~~~~~~~~~~~~
> kernel/kheaders.c: In function âikheaders_read_currentâ:
> kernel/kheaders.c:40:1: warning: control reaches end of non-void function
> [-Wreturn-type]
> }
>
>
> The reason for me to stay on v4.20 is that with v5.0-rc8 I don't have ebpf
> 'raw tracepoint' support any more on my arm64 board. But this issue is not
> related to your patch though.

I'm glad mainline fixed your issue though as you said in the other thread ;-)
I will refer to your email here later when doing backports if I hit the issue.

> Another point which supports the functionality your patch provides is the
> fact that maintainers don't want to see new TRACE_EVENTs in their code. So
> here your patch comes handy when using ebpf for tracing in embedded
> environments.

Yes, I agree. One can also use the series to build custom kernel modules
which can also contain tracepoints in their own right. Glad you also find it
useful. I will CC you on it for next spin.

thanks,

- Joel