On Fri, Oct 6, 2017 at 9:50 PM, kernelci.org bot bot@kernelci.org wrote:
stable-rc/linux-3.18.y build: 170 builds: 4 failed, 166 passed, 4 errors (v3.18.73-36-ge7bfc3a7bb75) Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.73-36-... Tree: stable-rc Branch: linux-3.18.y Git Describe: v3.18.73-36-ge7bfc3a7bb75 Git Commit: e7bfc3a7bb7560487107d3572dc67f8e762acbaf Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Built: 4 unique architectures
Build Failures Detected:
mips: gcc version 6.3.0 (GCC) ar7_defconfig FAIL lemote2f_defconfig FAIL loongson3_defconfig FAIL nlm_xlr_defconfig FAIL
Errors: arch/mips/kernel/setup.c:588:7: error: implicit declaration of function 'memory_region_available' [-Werror=implicit-function-declaration]
This is caused by c3628230f90f ("MIPS: kexec: Do not reserve invalid crashkernel memory on boot"), upstream c3628230f90f3.
The memory_region_available() function was introduced in linux-4.11 by commit d9b5b658210f ("MIPS: init: Ensure bootmem does not corrupt reserved memory"), but this patch has not been backported to stable kernels yet.
Right now, the stable-rc trees for 3.18 and 4.9 both have this problem, while 4.4 doesn't have a backport of c3628230f90f3 (yet).
I suppose we either want to have both patches in all stable kernels, or drop the c3628230f90f3 backport. Marcin Nowakowski might be able to offer some more insight, as he wrote both patches as part of a longer patch series. There might be other patches from that series that qualify for backports.
Arnd