On Tue, Jul 19, 2022 at 11:27:18PM +0530, Naresh Kamboju wrote:
On Tue, 19 Jul 2022 at 17:49, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 5.18.13 release. There are 231 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Thu, 21 Jul 2022 11:43:40 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.18.13-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.18.y and the diffstat can be found below.
thanks,
greg k-h
There are two regression found
Build regression on i386 with clang-13 and clang-14, I do not see this build error on mainline.
- Too many build warnings x86 with gcc-11
I do not see these build warnings on mainline,
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
Details log:
- i386 build failures with clang-13 and clang-14
make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build LLVM=1 LLVM_IAS=1 ARCH=i386 CROSS_COMPILE=i686-linux-gnu- 'HOSTCC=sccache clang' 'CC=sccache clang' ld.lld: error: undefined symbol: __udivdi3
referenced by i915_scatterlist.c gpu/drm/i915/i915_scatterlist.o:(i915_rsgt_from_mm_node) in archive drivers/built-in.a
make[1]: *** [/builds/linux/Makefile:1162: vmlinux] Error 1
steps to reproduce:
tuxmake --runtime podman --target-arch i386 --toolchain clang-14 --kconfig https://builds.tuxbuild.com/2CA3gjUTE2s74Bzp3G7q2hBxj1t/config LLVM=1 LLVM_IAS=1 [1] https://builds.tuxbuild.com/2CA3gjUTE2s74Bzp3G7q2hBxj1t/
- Large number of build warnings on x86 with gcc-11,
I do not see these build warnings on mainline,
Build link: https://builds.tuxbuild.com/2CA3fVEQKJXLNNGgHvoEmFEjyPq/
Very odd, can you do bisect to track down the offending commits?
My local building test system is not working for unrelated issues (local heat wave), and my cloud test systems are broken for some other unknown reason, so I can't test this myself.
thanks,
greg k-h