------------------- NOTE, this is the LAST 5.18.y stable release. This tree will be end-of-life after this one. Please move to 5.19.y at this point in time or let us know why that is not possible. -------------------
This is the start of the stable review cycle for the 5.18.19 release. There are 6 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 Sun, 21 Aug 2022 15:36:59 +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.19-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
------------- Pseudo-Shortlog of commits:
Greg Kroah-Hartman gregkh@linuxfoundation.org Linux 5.18.19-rc1
Coiby Xu coxu@redhat.com arm64: kexec_file: use more system keyrings to verify kernel image signature
Coiby Xu coxu@redhat.com kexec, KEYS: make the code in bzImage64_verify_sig generic
Qu Wenruo wqu@suse.com btrfs: raid56: don't trust any cached sector in __raid56_parity_recover()
Qu Wenruo wqu@suse.com btrfs: only write the sectors in the vertical stripe which has data stripes
Jamal Hadi Salim jhs@mojatatu.com net_sched: cls_route: disallow handle of 0
Jens Wiklander jens.wiklander@linaro.org tee: add overflow check in register_shm_helper()
-------------
Diffstat:
Makefile | 4 +-- arch/arm64/kernel/kexec_image.c | 11 +----- arch/x86/kernel/kexec-bzimage64.c | 20 +---------- drivers/tee/tee_shm.c | 3 ++ fs/btrfs/raid56.c | 74 ++++++++++++++++++++++++++++++--------- include/linux/kexec.h | 7 ++++ kernel/kexec_file.c | 17 +++++++++ net/sched/cls_route.c | 10 ++++++ 8 files changed, 98 insertions(+), 48 deletions(-)
On 8/19/22 9:40 AM, Greg Kroah-Hartman wrote:
NOTE, this is the LAST 5.18.y stable release. This tree will be end-of-life after this one. Please move to 5.19.y at this point in time or let us know why that is not possible.
This is the start of the stable review cycle for the 5.18.19 release. There are 6 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 Sun, 21 Aug 2022 15:36:59 +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.19-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
Compiled and booted on my test system. No dmesg regressions.
Tested-by: Shuah Khan skhan@linuxfoundation.org
thanks, -- Shuah
On Fri, 19 Aug 2022 at 21:10, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
NOTE, this is the LAST 5.18.y stable release. This tree will be end-of-life after this one. Please move to 5.19.y at this point in time or let us know why that is not possible.
This is the start of the stable review cycle for the 5.18.19 release. There are 6 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 Sun, 21 Aug 2022 15:36:59 +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.19-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
Results from Linaro's test farm. No regressions on arm64, arm, x86_64, and i386.
Tested-by: Linux Kernel Functional Testing lkft@linaro.org
## Build * kernel: 5.18.19-rc1 * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc * git branch: linux-5.18.y * git commit: f06dacf3d236cd8b16b2a869572c0e849f2aa156 * git describe: v5.18.18-7-gf06dacf3d236 * test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.18.y/build/v5.18....
## No test Regressions (compared to v5.18.18)
## No metric Regressions (compared to v5.18.18)
## No test Fixes (compared to v5.18.18)
## No metric Fixes (compared to v5.18.18)
## Test result summary total: 138885, pass: 123740, fail: 932, skip: 13421, xfail: 792
## Build Summary * arc: 10 total, 10 passed, 0 failed * arm: 313 total, 310 passed, 3 failed * arm64: 76 total, 74 passed, 2 failed * i386: 64 total, 58 passed, 6 failed * mips: 50 total, 47 passed, 3 failed * parisc: 14 total, 14 passed, 0 failed * powerpc: 65 total, 56 passed, 9 failed * riscv: 32 total, 27 passed, 5 failed * s390: 23 total, 20 passed, 3 failed * sh: 26 total, 24 passed, 2 failed * sparc: 14 total, 14 passed, 0 failed * x86_64: 69 total, 67 passed, 2 failed
## Test suites summary * fwts * igt-gpu-tools * kunit * kvm-unit-tests * libgpiod * libgpiod[ * libhugetlbfs * log-parser-boot * log-parser-test * ltp-cap_bounds * ltp-commands * ltp-containers * ltp-controllers * ltp-cpuhotplug * ltp-crypto * ltp-cve * ltp-dio * ltp-fcntl-locktests * ltp-filecaps * ltp-fs * ltp-fs_bind * ltp-fs_perms_simple * ltp-fsx * ltp-hugetlb * ltp-io * ltp-ipc * ltp-math * ltp-mm * ltp-nptl * ltp-open-posix-tests * ltp-pty * ltp-sched * ltp-securebits * ltp-smoke * ltp-syscalls * ltp-tracing * network-basic-tests * packetdrill * rcutorture * ssuite * v4l2-compliance * vdso
-- Linaro LKFT https://lkft.linaro.org
On 8/19/22 8:40 AM, Greg Kroah-Hartman wrote:
NOTE, this is the LAST 5.18.y stable release. This tree will be end-of-life after this one. Please move to 5.19.y at this point in time or let us know why that is not possible.
This is the start of the stable review cycle for the 5.18.19 release. There are 6 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 Sun, 21 Aug 2022 15:36:59 +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.19-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
Built and booted successfully on RISC-V RV64 (HiFive Unmatched).
Tested-by: Ron Economos re@w6rz.net
Hi Greg,
On Fri, Aug 19, 2022 at 05:40:12PM +0200, Greg Kroah-Hartman wrote:
NOTE, this is the LAST 5.18.y stable release. This tree will be end-of-life after this one. Please move to 5.19.y at this point in time or let us know why that is not possible.
This is the start of the stable review cycle for the 5.18.19 release. There are 6 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 Sun, 21 Aug 2022 15:36:59 +0000. Anything received after that time might be too late.
Build test (gcc version 12.2.1 20220819): mips: 59 configs -> 1 failure arm: 99 configs -> no failure arm64: 3 configs -> no failure x86_64: 4 configs -> no failure alpha allmodconfig -> no failure csky allmodconfig -> fails powerpc allmodconfig -> fais riscv allmodconfig -> no failure s390 allmodconfig -> no failure xtensa allmodconfig -> no failure
Note: csky and mips allmodconfig fails with gcc-12, passes with gcc-11. Already reported for mainline.
powerpc failure is not seen in mainline. Same error as csky and mips.
In function 'memcmp', inlined from 'bacmp' at ./include/net/bluetooth/bluetooth.h:302:9, inlined from 'l2cap_global_chan_by_psm' at net/bluetooth/l2cap_core.c:2002:15: ./include/linux/fortify-string.h:44:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread] 44 | #define __underlying_memcmp __builtin_memcmp | ^ ./include/linux/fortify-string.h:404:16: note: in expansion of macro '__underlying_memcmp' 404 | return __underlying_memcmp(p, q, size); | ^~~~~~~~~~~~~~~~~~~ In function 'memcmp', inlined from 'bacmp' at ./include/net/bluetooth/bluetooth.h:302:9, inlined from 'l2cap_global_chan_by_psm' at net/bluetooth/l2cap_core.c:2003:15: ./include/linux/fortify-string.h:44:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread] 44 | #define __underlying_memcmp __builtin_memcmp | ^ ./include/linux/fortify-string.h:404:16: note: in expansion of macro '__underlying_memcmp' 404 | return __underlying_memcmp(p, q, size); | ^~~~~~~~~~~~~~~~~~~
I am bisecting now to find out what caused it.
Boot test: x86_64: Booted on my test laptop. No regression. x86_64: Booted on qemu. No regression. [1] mips: Booted on ci20 board. No regression. [2]
[1]. https://openqa.qa.codethink.co.uk/tests/1660 [2]. https://openqa.qa.codethink.co.uk/tests/1667
Tested-by: Sudip Mukherjee sudip.mukherjee@codethink.co.uk
-- Regards Sudip
On Sat, Aug 20, 2022 at 11:03 AM Sudip Mukherjee (Codethink) sudipm.mukherjee@gmail.com wrote:
Hi Greg,
On Fri, Aug 19, 2022 at 05:40:12PM +0200, Greg Kroah-Hartman wrote:
NOTE, this is the LAST 5.18.y stable release. This tree will be end-of-life after this one. Please move to 5.19.y at this point in time or let us know why that is not possible.
This is the start of the stable review cycle for the 5.18.19 release. There are 6 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 Sun, 21 Aug 2022 15:36:59 +0000. Anything received after that time might be too late.
<snip>
powerpc failure is not seen in mainline. Same error as csky and mips.
In function 'memcmp', inlined from 'bacmp' at ./include/net/bluetooth/bluetooth.h:302:9, inlined from 'l2cap_global_chan_by_psm' at net/bluetooth/l2cap_core.c:2002:15: ./include/linux/fortify-string.h:44:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread] 44 | #define __underlying_memcmp __builtin_memcmp | ^ ./include/linux/fortify-string.h:404:16: note: in expansion of macro '__underlying_memcmp' 404 | return __underlying_memcmp(p, q, size); | ^~~~~~~~~~~~~~~~~~~ In function 'memcmp', inlined from 'bacmp' at ./include/net/bluetooth/bluetooth.h:302:9, inlined from 'l2cap_global_chan_by_psm' at net/bluetooth/l2cap_core.c:2003:15: ./include/linux/fortify-string.h:44:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread] 44 | #define __underlying_memcmp __builtin_memcmp | ^ ./include/linux/fortify-string.h:404:16: note: in expansion of macro '__underlying_memcmp' 404 | return __underlying_memcmp(p, q, size); | ^~~~~~~~~~~~~~~~~~~
I am bisecting now to find out what caused it.
Introduced in v5.18.18 due to 11e008e59970 ("Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm regression"). But v5.19.y and mainline does not show the build failure as they also have 41b7a347bf14 ("powerpc: Book3S 64-bit outline-only KASAN support").
On Sat, Aug 20, 2022 at 11:32:36AM +0100, Sudip Mukherjee wrote:
On Sat, Aug 20, 2022 at 11:03 AM Sudip Mukherjee (Codethink) sudipm.mukherjee@gmail.com wrote:
Hi Greg,
On Fri, Aug 19, 2022 at 05:40:12PM +0200, Greg Kroah-Hartman wrote:
NOTE, this is the LAST 5.18.y stable release. This tree will be end-of-life after this one. Please move to 5.19.y at this point in time or let us know why that is not possible.
This is the start of the stable review cycle for the 5.18.19 release. There are 6 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 Sun, 21 Aug 2022 15:36:59 +0000. Anything received after that time might be too late.
<snip>
powerpc failure is not seen in mainline. Same error as csky and mips.
In function 'memcmp', inlined from 'bacmp' at ./include/net/bluetooth/bluetooth.h:302:9, inlined from 'l2cap_global_chan_by_psm' at net/bluetooth/l2cap_core.c:2002:15: ./include/linux/fortify-string.h:44:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread] 44 | #define __underlying_memcmp __builtin_memcmp | ^ ./include/linux/fortify-string.h:404:16: note: in expansion of macro '__underlying_memcmp' 404 | return __underlying_memcmp(p, q, size); | ^~~~~~~~~~~~~~~~~~~ In function 'memcmp', inlined from 'bacmp' at ./include/net/bluetooth/bluetooth.h:302:9, inlined from 'l2cap_global_chan_by_psm' at net/bluetooth/l2cap_core.c:2003:15: ./include/linux/fortify-string.h:44:33: error: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Werror=stringop-overread] 44 | #define __underlying_memcmp __builtin_memcmp | ^ ./include/linux/fortify-string.h:404:16: note: in expansion of macro '__underlying_memcmp' 404 | return __underlying_memcmp(p, q, size); | ^~~~~~~~~~~~~~~~~~~
I am bisecting now to find out what caused it.
Introduced in v5.18.18 due to 11e008e59970 ("Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm regression"). But v5.19.y and mainline does not show the build failure as they also have 41b7a347bf14 ("powerpc: Book3S 64-bit outline-only KASAN support").
Ick, that's a mess. This is going to be the last 5.18 tree, so I'm just going to leave this alone...
thanks,
greg k-h
On Fri, Aug 19, 2022 at 05:40:12PM +0200, Greg Kroah-Hartman wrote:
NOTE, this is the LAST 5.18.y stable release. This tree will be end-of-life after this one. Please move to 5.19.y at this point in time or let us know why that is not possible.
This is the start of the stable review cycle for the 5.18.19 release. There are 6 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 Sun, 21 Aug 2022 15:36:59 +0000. Anything received after that time might be too late.
Build results: total: 154 pass: 154 fail: 0 Qemu test results: total: 487 pass: 486 fail: 1 Failed tests: arm:bletchley-bmc:aspeed_g5_defconfig:notests:usb0:net,nic:aspeed-bmc-facebook-bletchley:rootfs
No new failures. As with v5.15.y, I did not receive this e-mail and had to copy it from lore instead.
Tested-by: Guenter Roeck linux@roeck-us.net
Guenter