Right now the reproducer is poky scarthgap, meta-arm master (or scarthgap if it exists when you read this), MACHINE=sbsa-ref, linux-yocto-dev: | MODPOST vmlinux.symvers | ERROR: modpost: vmlinux: local symbol 'security_path_rmdir' was exported | make[2]: *** [/work/ross/build/tmp/work-shared/sbsa-ref/kernel-source/scripts/Makefile.modpost:145: vmlinux.symvers] Error 1 | make[1]: *** [/work/ross/build/tmp/work-shared/sbsa-ref/kernel-source/Makefile:1871: modpost] Error 2 | make: *** [/work/ross/build/tmp/work-shared/sbsa-ref/kernel-source/Makefile:240: __sub-make] Error 2 | ERROR: oe_runmake failed
Interestingly sbsa-ref is a qemu-based machine using the defconfig kernel, but if I add this then it doesn't fail: KBUILD_DEFCONFIG:qemuarm46 = "defconfig" KCONFIG_MODE:qemuarm46 = "--alldefconfig" Why that is remains a mystery.
Bulk move of medium importance bugs from 5.1 to 5.2 on behalf of Bruce.
I can still replicate this with scarthgap and linux-yocto-dev.
What is qemuarm46?
Ross to retest with a 64 bit system, rather than the mystery 46 bit system.
Our CI still replicates this with sbsa-ref/alldefconfig/linux-yocto-dev on scarthgap, but not wrynose or master. Testing qemuarm64 now...
This only reproduces with linux-yocto-dev on scarthgap; Ross confirmed it does not reproduce on wrynose or master. linux-yocto-dev tracks master and isn't a supported combination on the scarthgap release branch, so I'm closing this out. If it shows up with linux-yocto-dev on master, please reopen.