> /proc/kheaders.txz This is gross.
> The feature is also buildable as a module just in case the user desires > it not being part of the kernel image. This makes it possible to load > and unload the headers on demand. A tracing program, or a kernel module > builder can load the module, do its operations, and then unload the > module to save kernel memory. Please explain how keeping headers on the filesystem is not OK due to "licensing and other issues" but keeping a module on the filesystem is OK. > > I can route it via bpf-next tree if there are no objections. Please don't. IKHD_ST IKHD_ED are bogus artifacts as others mentioned. proc_create(S_IFREG) is redundant. seq_file.h is not needed as is THIS_MODULE. I'd say such data should live in their own section for easy extraction with "objdump -j", something /proc/config.gz never did.
