Verifying Parser Output: Missing files about kbuildparser

[rupran]

Hi, and thanks for using my tool!

I think I can explain most of them.

• All the .mod.c files do not actually exist, their corresponding .o counterparts are generated during the build for loadable kernel modules.
• Some .o files (like llc.o) do not have a corresponding .c file, but the rules in Kbuild produce a file of that name, see for example https://elixir.bootlin.com/linux/v5.4.35/source/net/llc/Makefile#L15 and the llc-y rule below the highlighted line.
• Our tool does not descend into scripts/ as the binary files in that directory are not part of the kernel image.
• The files inside arch/arm64/lib/ are mostly written in Assembly, so instead of memset.c there is a file memset.S.
• For most of the remaining files in arch/arm64, my tool does generate an output line but does not list any precondition - because the file is always part of the build as a result of being added to obj-y in a top level directory - so something like

[...]
arch/arm64/kernel/sleep.S <- CONFIG_CPU_PM
arch/arm64/kernel/smccc-call.S
arch/arm64/kernel/smp.c
[...]

is perfectly valid and simply means that the last two files do not have any precondition.

• Lastly, the files in drivers/firmware/efi/libstub also seem to not be part of the kernel image itself as they get built through lib-... lists which our work didn't need to cover.

If there are any more cases that are unclear, let me know!

[riskyblooky]

Wow, Thanks for your quick and thorough reply.
I think that covers most the cases and explains the behavior.

Thanks for the great tool!